LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37889: WordPress WPAdmin AWS CDN Plugin <= 2.0.13 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in WPAdmin WPAdmin AWS CDN plugin <= 2.0.13 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-risk CSRF issue in the WordPress WPAdmin AWS CDN plugin through version 2.0.13. An attacker would need a logged-in user to interact with attacker-controlled content. The expected impact is limited unauthorized change, not data theft or outage. The provided sources do not report active exploitation.

Executive priority

Handle during normal vulnerability remediation cycles, with faster action for business-critical WordPress sites or administrator-heavy workflows. The issue is not currently KEV-listed and has limited impact, but exposed plugins still create avoidable site integrity risk.

Technical view

CVE-2023-37889 is CWE-352 CSRF with CVSS 3.1 score 4.3: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The affected product is WPAdmin AWS CDN for WordPress, package aws-cdn-by-wpadmin, through 2.0.13. Sources do not identify the vulnerable action, fixed version, or proof-of-concept details.

Likely exposure

Exposure is likely limited to WordPress sites that installed and still run WPAdmin AWS CDN version 2.0.13 or earlier. Sites without this plugin are not affected based on the supplied sources.

Exploitation context

The CVSS vector requires user interaction and no attacker privileges. The source bundle says KEV is false and provides no evidence of active exploitation. Treat exploitation status as unconfirmed, not known-exploited.

Researcher notes

The public bundle is sparse. It confirms CSRF, affected plugin/version range, CVSS, CWE, and Patchstack reference, but not the exact endpoint/action, nonce failure, fixed release, or exploit availability. Avoid asserting those details without additional vendor evidence.

Mitigation direction

  • Inventory WordPress sites for the aws-cdn-by-wpadmin plugin.
  • Check WPAdmin or Patchstack guidance for a fixed version or vendor mitigation.
  • Update if a vendor-supported fixed release is available.
  • Disable or remove the plugin where it is not required.
  • Limit administrator browsing from logged-in WordPress sessions.

Validation and detection

  • Confirm whether WPAdmin AWS CDN is installed on each WordPress site.
  • Record installed plugin versions and flag 2.0.13 or earlier.
  • Review vendor and Patchstack advisories for current remediation guidance.
  • Verify no unsupported assumptions about affected actions or fixes are used.
  • Track remediation status for each exposed WordPress instance.
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-37889 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
4.3 (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:N

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

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-37889Attack 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:N

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
WPAdminWPAdmin AWS CDNaws-cdn-by-wpadmin, 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.