Skip to main content
VulnerabilityPublished Updated

CVE-2026-2281: Private Comment (WordPress plugin) · Cross-site Scripting

Affects Private Comment (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
edersonpekaPrivate CommentAffected
  • <=0.0.4
Fixed in–

AI-suggested

Administrators should limit administrator-level access to trusted users and consider disabling or avoiding use of the Private Comment plugin on multi-site installations where unfiltered_html is disabled until a fix is released. Monitor the vendor's advisory channels for updates regarding remediation.

Description

The Private Comment plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Label text' setting in all versions up to, and including, 0.0.4. This is due to insufficient input sanitization and output escaping on the plugin's label text option. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

References

Community reviews

Loading reviews…