LiveActive security incident?Get immediate response
CVE Record

CVE-2023-28986: WordPress Affiliates Manager Plugin <= 2.9.20 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in wp.Insider, wpaffiliatemgr Affiliates Manager plugin <= 2.9.20 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-28986 is a CSRF issue in the WordPress Affiliates Manager plugin up to 2.9.20. It could let an attacker trick a user into causing unwanted plugin actions. The reported impact is limited, but affected WordPress sites should verify exposure and follow vendor guidance.

Executive priority

Treat as a moderate WordPress application risk. It is not reported as actively exploited in the provided evidence, but affected public sites should be checked promptly because CSRF issues can cause unwanted administrative or operational changes.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in wp.Insider/wpaffiliatemgr Affiliates Manager package affiliates-manager <= 2.9.20. CVSS 3.1 is 5.4: network reachable, low complexity, no privileges required, user interaction required, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress sites running the Affiliates Manager plugin at version 2.9.20 or earlier. The source bundle does not provide CPEs or a complete affected-version matrix beyond the <= 2.9.20 statement.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector requires user interaction, consistent with a CSRF scenario where a victim must be induced to perform an unwanted browser-mediated action.

Researcher notes

Evidence is sparse. The CVE gives CWE-352 and CVSS details, while Patchstack is the only vulnerability database reference in the bundle. No exploit details, affected endpoint, fixed version, or mitigation specifics are provided here, so validation should stay version- and advisory-driven.

Mitigation direction

  • Inventory WordPress sites for the affiliates-manager plugin and installed version.
  • Check vendor and Patchstack guidance for the fixed or recommended version.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Prioritize sites with administrator or affiliate-management users at phishing risk.

Validation and detection

  • Confirm whether each WordPress site runs Affiliates Manager <= 2.9.20.
  • Record plugin version evidence from WordPress administration or asset inventory.
  • Review vendor or Patchstack advisory status before closing remediation.
  • Verify the plugin is updated, disabled, or otherwise risk-accepted.
  • Document any compensating controls and remaining business exposure.
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-28986 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-28986Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
wp.insider, wpaffiliatemgrAffiliates Manageraffiliates-manager, 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.