LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47652: WordPress Auto Affiliate Links Plugin <= 6.4.2.4 is vulnerable to Cross Site Request Forgery (CSRF)

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A WordPress plugin used for affiliate link automation can be abused through CSRF to create stored cross-site scripting. The business risk is site compromise impact through malicious script execution, but the provided sources do not show active exploitation or identify a fixed version.

Executive priority

Treat as high priority for WordPress properties using this plugin, especially public or revenue-generating sites. Prioritize inventory first because exposure depends entirely on plugin presence and version. Do not assume active exploitation from the provided evidence.

Technical view

CVE-2023-47652 is a CWE-352 CSRF issue in Lucian Apostol Auto Affiliate Links through 6.4.2.4 that allows Stored XSS. CVSS 3.1 is 7.1 high: network reachable, low complexity, no attacker privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running Auto Affiliate Links at affected versions through 6.4.2.4. The source bundle does not provide CPEs, install base, affected endpoints, or required victim role.

Exploitation context

The CVE is not marked KEV, and the supplied sources do not state active exploitation. Exploitation requires user interaction. The sources do not provide exploit maturity, public proof-of-concept status, or detailed attack preconditions.

Researcher notes

The public record is sparse. It identifies CSRF leading to Stored XSS and a high CVSS score, but does not name the vulnerable request, nonce failure, affected role, fixed version, or exploitation in the wild. Validate defensively without developing exploit steps.

Mitigation direction

  • Inventory WordPress sites for the Auto Affiliate Links plugin and version.
  • Check vendor and Patchstack guidance for a fixed release or official remediation.
  • Update the plugin if an official fixed version is available.
  • Disable or remove the plugin where business impact is acceptable pending vendor guidance.
  • Review WordPress administrative access and reduce unnecessary privileged accounts.

Validation and detection

  • Confirm whether Auto Affiliate Links is installed on each WordPress site.
  • Record the installed plugin version and compare it to 6.4.2.4 or earlier.
  • Check Patchstack and vendor channels for remediation status.
  • Review WordPress content and settings for unexpected stored script content.
  • Look for recent suspicious administrative changes around plugin-managed link settings.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47652 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-47652Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Lucian ApostolAuto Affiliate Linkswp-auto-affiliate-links, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.