dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-1647

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Comment Genius plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `$_SERVER['PHP_SELF']` parameter in all versions up to, and including, 1.2.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Comment Genius WordPress plugin up to version 1.2.5 contains a reflected cross-site scripting (XSS) vulnerability via the $_SERVER['PHP_SELF'] parameter due to insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript through malicious links.

MitigationUpdate to a patched version if available; otherwise, apply proper sanitization to the PHP_SELF parameter and ensure all output is escaped before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Comment Genius plugin
    Check the wp-content/plugins/ directory for a folder named 'comment-genius' or similar. In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for Comment Genius.
    Affected if The Comment Genius plugin is not found in the plugins directory or not listed in the WordPress admin
  2. Identify the installed version
    Open the main plugin PHP file (usually comment-genius.php) and check the plugin header for the 'Version' field, or check the readme.txt file.
    Affected if The reported version is 1.2.5 or any lower version number
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm Comment Genius shows as 'Active'.
    Affected if The plugin is active and vulnerable code can be executed
  4. Search for PHP_SELF usage in plugin files
    Use grep or a file search to find all occurrences of $_SERVER['PHP_SELF'] within the Comment Genius plugin directory.
    Affected if $_SERVER['PHP_SELF'] is found in any PHP file within the plugin
  5. Check for proper sanitization of PHP_SELF output
    Examine the code around each $_SERVER['PHP_SELF'] usage. Look for functions like esc_html(), esc_attr(), htmlspecialchars(), or other sanitization functions applied before echoing or rendering the value.
    Affected if $_SERVER['PHP_SELF'] is echoed or output without being passed through sanitization functions

You are affected if the Comment Genius plugin version is 1.2.5 or earlier, the plugin is active, and its PHP files output $_SERVER['PHP_SELF'] without proper sanitization or escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version if available; otherwise, apply proper sanitization to the PHP_SELF parameter and ensure all output is escaped before rendering.

Recommended fix Moderate confidence

Version 1.2.6 or later (any version higher than 1.2.5)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the Comment Genius plugin in the list
  3. 3. If an update is available, click 'Update Now' to install the latest version
  4. 4. Alternatively, download the latest version from the WordPress Plugin Repository at wordpress.org/plugins/comment-genius/
  5. 5. Deactivate and delete the current version, then upload and activate the new version
  6. 6. Verify the plugin is functioning correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1647 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1647 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data