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

CVE-2025-22552

HIGH · 7.1 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in bnielsen Affiliate Disclosure Statement affiliate-disclosure-statement allows Cross Site Request Forgery.This issue affects Affiliate Disclosure Statement: from n/a through <= 0.3.

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

Cross-Site Request Forgery (CSRF) vulnerability in the bnielsen Affiliate Disclosure Statement WordPress plugin (versions <= 0.3). An attacker can craft malicious requests that trick authenticated administrators into performing unintended actions (such as modifying affiliate disclosure settings) without their knowledge, due to missing or insufficient anti-CSRF token validation on state-changing operations.

MitigationImplement WordPress nonces (wp_nonce_field/wp_verify_nonce) on all forms and administrative actions within the plugin to validate request origin and intent. Verify that all POST/GET requests that modify plugin settings include and validate anti-CSRF tokens.

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
Low

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

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 plugin is installed
    Look for the 'bnielsen-affiliate-disclosure-statement' directory in your WordPress wp-content/plugins folder, or check the Plugins list in WP admin for this plugin
    Affected if The plugin directory or listing exists in the WordPress installation
  2. Check installed version
    Open the main plugin PHP file (usually named affiliate-disclosure-statement.php or similar in the plugin directory) and locate the 'Version:' header in the plugin comment block; compare this version number to 0.3
    Affected if The reported version is 0.3 or lower
  3. Identify admin action handlers
    Search the plugin PHP files for functions that handle form submissions or URL parameters which modify plugin settings (look for 'add_action' hooks with 'admin_post_', 'init', or AJAX handlers that process POST/GET requests to change settings)
    Affected if The plugin contains functions that process settings changes via HTTP requests
  4. Verify nonce validation exists
    In the identified admin action handler functions, search for 'wp_verify_nonce', 'check_admin_referer', or 'wp_nonce_field' calls; check whether these nonce checks are present and properly used before any state-changing database operations
    Affected if The action handlers that modify settings lack nonce verification calls or do not validate nonces before processing requests

A user is affected if the bnielsen Affiliate Disclosure Statement plugin (version 0.3 or lower) is installed AND its admin settings handlers do not validate anti-CSRF tokens before processing state-changing requests.

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

Implement WordPress nonces (wp_nonce_field/wp_verify_nonce) on all forms and administrative actions within the plugin to validate request origin and intent. Verify that all POST/GET requests that modify plugin settings include and validate anti-CSRF tokens.

Recommended fix Moderate confidence

Latest version newer than 0.3 (update to current release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Affiliate Disclosure Statement' plugin by bnielsen
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is working correctly and the CSRF protection is in place
  6. 6. If no update is available in the WordPress repository, manually download the latest version from a trusted source and reinstall

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-2025-22552 — 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-2025-22552 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