CVE-2026-8626
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 · uneditedThe SponsorMe plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_SELF Parameter in all versions up to, and including, 0.5.2 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. The PHP_SELF value is reflected in two separate locations within the vulnerable function — a form action attribute and an anchor href attribute — both of which can be exploited by appending a crafted payload to the wp-admin/admin.php URL path.
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 confidenceThe SponsorMe WordPress plugin (versions up to 0.5.2) contains a reflected XSS vulnerability where the PHP_SELF server variable is directly used in form action and anchor href attributes within wp-admin/admin.php without sanitization or escaping, allowing script injection via crafted URLs.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify SponsorMe plugin installationLocate the SponsorMe plugin directory in your WordPress plugins folder and check the main plugin file header for the Version attributeAffected if The plugin is found with a version of 0.5.2 or lower listed in the plugin header
-
Verify plugin is activeCheck the WordPress database wp_options table for the option 'active_plugins' or use the WordPress admin plugins list to confirm SponsorMe is enabledAffected if SponsorMe appears in the list of active plugins
-
Check plugin source for vulnerable PHP_SELF usageExamine the main plugin PHP files (typically sponsorme.php or similar) and search for occurrences of 'PHP_SELF' that are output directly without sanitization functions such as esc_attr() or htmlspecialchars()Affected if Code contains $_SERVER['PHP_SELF'] or similar being echoed or printed without sanitization in admin-facing pages
-
Confirm admin page contextInspect the plugin files for admin menu registration and page rendering functions (add_menu_page, add_submenu_page, or admin_menu hooks) that handle the vulnerable PHP_SELF outputAffected if The plugin registers admin pages under wp-admin and the unsanitized PHP_SELF appears in form action or anchor href attributes within those pages
Your environment is affected if SponsorMe plugin versions 0.5.2 or lower are installed and active, and the plugin code outputs the PHP_SELF server variable without sanitization in admin pages.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to a patched version of the SponsorMe plugin once available, or apply manual escaping using WordPress functions like esc_attr() and esc_url() to the PHP_SELF output in the vulnerable code locations.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-8626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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