dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-8906

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-27
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 WP Promoter plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator 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 · moderate confidence

The WP Promoter WordPress plugin versions up to 1.3 is vulnerable to Cross-Site Request Forgery due to missing or incorrect nonce validation on a settings function. This allows unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious web scripts, provided they can trick a site administrator into clicking a malicious link.

MitigationUpdate the WP Promoter plugin to a patched version if available, and ensure all plugin functions that modify settings or perform administrative actions implement proper nonce validation and CSRF token checks.

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. Verify WP Promoter plugin is installed
    Check the WordPress plugins directory for the wp-promoter folder, or look for WP Promoter in the WordPress admin plugins list
    Affected if WP Promoter plugin is found installed and active on the site
  2. Determine installed plugin version
    Open the main plugin file (usually wp-promoter.php) and check the version header, or check the plugin row in WordPress admin plugins page
    Affected if The installed version is 1.3 or earlier
  3. Inspect settings function for nonce validation
    Locate the PHP file containing the settings function that modifies plugin options and examine the code forwp_verify_nonce or check_admin_referer calls before processing settings changes
    Affected if The settings function lacks proper nonce verification or uses an incorrect/inadequate nonce check
  4. Review plugin settings for unauthorized changes
    Access the WP Promoter settings page in WordPress admin and examine all saved option values for suspicious URLs, scripts, or unexpected content
    Affected if Settings contain unexpected JavaScript URLs, base64-encoded scripts, or values not set by legitimate administrators

The environment is affected if WP Promoter version 1.3 or earlier is installed AND the plugin settings function is missing or has incorrect nonce validation, allowing CSRF attacks to modify settings.

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 the WP Promoter plugin to a patched version if available, and ensure all plugin functions that modify settings or perform administrative actions implement proper nonce validation and CSRF token checks.

Recommended fix Moderate confidence

Latest version of WP Promoter plugin (version higher than 1.3)

  1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. Locate the WP Promoter plugin and check if an update is available
  3. If an update is available, update to the latest version of the WP Promoter plugin
  4. If no update is available through the WordPress admin, visit the WordPress plugin repository (plugins.trac.wordpress.org) to manually download the latest version
  5. After updating, verify that the plugin settings cannot be modified via forged requests by confirming nonce validation is implemented in the plugin code
  6. Monitor the plugin's changelog or security advisories for any further updates

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8906 — 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-8906 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