dbcve.org
Affiliates ManagerWordPress extension · Wpaffiliatemanager

CVE-2023-52130

HIGH · 8.8 CVSS v3.1 Published 2024-01-05
Fix available
A fix is available. Upgrade to after 2.9.31 or later.
See remediation →
95/100
Remediation priority · Urgent
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 wp.Insider, wpaffiliatemgr Affiliates Manager.This issue affects Affiliates Manager: from n/a through 2.9.31.

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 WordPress Affiliates Manager plugin (versions up to 2.9.31) allows attackers to induce authenticated users to perform unintended administrative actions via maliciously crafted requests.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations, validate referer headers, and add SameSite cookie attributes.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Affiliates ManagerWordPress extension
Affected:<= 2.9.31

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Affiliates Manager' (or 'Wpaffiliatemanager'), and record the version number displayed. Alternatively, inspect the plugin's main PHP file (typically wp-content/plugins/affiliates-manager/core/wpam-core.php or similar) and look for the 'Version:' header comment.
    Affected if Version listed is 2.9.31 or lower, or no version is displayed but the plugin name matches 'Affiliates Manager' or 'Wpaffiliatemanager'.
  2. Identify state-changing admin actions
    Review the plugin's PHP source code for functions that perform administrative tasks such as creating/updating affiliates, modifying settings, or changing user roles. Look for form handlers and AJAX endpoints that process requests which alter data.
    Affected if The plugin processes requests that modify affiliate data, settings, or user permissions without obvious token validation.
  3. Inspect for nonce token validation
    Open the plugin's PHP files and search for 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', 'wp_verify_nonce', or 'check_ajax_referer' function calls within the identified state-changing action handlers. Record whether these nonce verification functions are present and properly implemented.
    Affected if State-changing operations lack nonce verification calls, or nonces are generated but never validated before executing the action.
  4. Check referer header validation
    Search the plugin code for '$_SERVER["HTTP_REFERER"]' or 'wp_referer_field' usage. Determine if the HTTP Referer or Origin header is validated before processing any administrative request.
    Affected if No referer or Origin header validation exists in the request handling logic for administrative actions.
  5. Verify SameSite cookie attributes
    If the plugin sets any custom cookies, inspect the code for 'setcookie' or 'setrawcookie' calls. Check if the 'SameSite' attribute is included with values such as 'Strict' or 'Lax', or if the session cookie configuration in WordPress includes this attribute.
    Affected if Cookies related to affiliate functionality are set without the SameSite attribute, or SameSite is set to 'None' without the 'Secure' flag.

The environment is affected if the Affiliates Manager plugin is installed with version 2.9.31 or lower and the code handling administrative actions lacks proper nonce verification, referer validation, and SameSite cookie attributes.

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.

From vendor data
Upgrade available Upgrade to a release after 2.9.31
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations, validate referer headers, and add SameSite cookie attributes.

Fix this in Affiliates Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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