dbcve.org
Auto Affiliate LinksWordPress extension · Flamescorpion

CVE-2023-47652

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to 6.4.2.5 or later.
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
Cross-Site Request Forgery (CSRF) vulnerability in Lucian Apostol Auto Affiliate Links allows Stored XSS.This issue affects Auto Affiliate Links: from n/a through 6.4.2.4.

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

This is a CSRF vulnerability in the Auto Affiliate Links plugin that allows attackers to inject stored XSS payloads. An attacker can craft a malicious link that, when clicked by an authenticated administrator, forces the browser to submit a request that stores malicious JavaScript in the plugin's settings or link database. This stored XSS then executes in the browsers of other users who view the affected content.

MitigationUpdate to the latest version of Auto Affiliate Links if a patch is available; otherwise, implement anti-CSRF token validation on all state-changing plugin actions and ensure administrators are aware of phishing risks.

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
Auto Affiliate LinksWordPress extension
Affected:< 6.4.2.5

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 the Auto Affiliate Links plugin is installed
    Check your WordPress installation's plugin directory or use wp plugin list to list installed plugins and look for 'auto-affiliate-links' or 'flamescorpion-auto-affiliate-links'
    Affected if The plugin is present in the installation
  2. Determine the installed plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, find Auto Affiliate Links, and note the version number displayed, or use 'wp plugin get auto-affiliate-links' via WP-CLI
    Affected if The version number is lower than 6.4.2.5
  3. Check plugin settings for stored XSS payloads
    Navigate to the plugin's settings page (usually under Settings > Auto Affiliate Links in WordPress admin) and inspect any fields that store URLs, link titles, or anchor text. Manually review the link database table (commonly wp_auto_affiliate_links or similar) for suspicious JavaScript tags in stored values.
    Affected if Any stored links contain script tags, event handlers (onclick, onerror, etc.), or other JavaScript code in URL or text fields
  4. Review admin activity for potential CSRF exploitation
    Check WordPress audit logs or access logs for POST requests to plugin admin endpoints (ajax.php, admin-post.php, or plugin-specific handlers) that coincide with suspicious link insertions, especially from unexpected referrers or during periods the admin did not intentionally modify links
    Affected if There are admin actions adding links that were not initiated by a legitimate admin session or contain encoded/suspicious content
  5. Inspect page output for injected scripts
    View the source of pages where affiliate links are displayed (typically in post content or sidebars) and search for unexpected script tags, iframe embeds, or modified link href attributes that differ from what is stored in the plugin database
    Affected if Rendered pages display JavaScript code or execute scripts that are not intentionally configured in the plugin

You are affected if the Flamescorpion Auto Affiliate Links plugin version is below 6.4.2.5 and your plugin database or settings contain any unauthorized or malicious script injections that were not intentionally added by your administrators.

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
Upgrade available Upgrade to 6.4.2.5 or later
Fixed in 6.4.2.5
Interim mitigation

Update to the latest version of Auto Affiliate Links if a patch is available; otherwise, implement anti-CSRF token validation on all state-changing plugin actions and ensure administrators are aware of phishing risks.

Recommended fix High confidence

Auto Affiliate Links version 6.4.2.5 or latest available version

  1. Update the Auto Affiliate Links plugin to version 6.4.2.5 or later through the WordPress admin dashboard under Plugins > Updates, or download the latest version from the WordPress plugin repository
  2. After updating, verify the new version is installed by checking the Plugins page in WordPress admin
  3. Consider reviewing any recently added affiliate links in the plugin to ensure no malicious content was injected via the CSRF/XSS vulnerability

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

Fix this in Auto Affiliate Links Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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