LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38512: WordPress WpStream plugin <= 4.5.4 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in wpstream WpStream wpstream allows Cross Site Request Forgery.This issue affects WpStream: from n/a through <= 4.5.4.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-38512 is a CSRF issue in the WordPress WpStream plugin through version 4.5.4. A malicious site could try to make a logged-in WordPress user’s browser perform unwanted WpStream-related actions. The available sources rate it medium, with limited integrity and availability impact and no confidentiality impact.

Executive priority

Treat as a moderate website platform risk. It is not listed as actively exploited in the provided evidence, but affected WordPress sites should be identified and remediated during normal patch cycles, sooner for revenue-generating video or pay-per-view services.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in wpstream WpStream. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, and low integrity and availability impact. The source bundle does not identify specific vulnerable endpoints or a fixed version.

Likely exposure

Exposure is limited to WordPress sites running the WpStream plugin at versions through 4.5.4. Risk is higher where privileged WordPress users remain logged in while browsing untrusted sites. The affected-version metadata is sparse beyond the <=4.5.4 statement.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation would require user interaction, typically a targeted logged-in WordPress user visiting attacker-controlled content. Public sources provided do not include proof-of-concept details.

Researcher notes

The public bundle confirms CSRF classification, CVSS, and affected range through 4.5.4, but lacks endpoint, nonce, capability-check, patch, or exploit details. Avoid claiming exploitation or a specific fix without additional vendor evidence.

Mitigation direction

  • Inventory WordPress sites for the WpStream plugin and installed version.
  • Check WpStream or Patchstack guidance for a fixed version or vendor mitigation.
  • Upgrade if vendor guidance confirms a patched release.
  • Disable or remove WpStream where it is not business-critical.
  • Reduce unnecessary privileged WordPress sessions on affected sites.

Validation and detection

  • Confirm each WordPress site’s installed WpStream version.
  • Verify whether any site is running WpStream version 4.5.4 or earlier.
  • Review WordPress administrative activity for unexpected WpStream configuration changes.
  • Confirm remediation against vendor or Patchstack guidance, not assumptions.
  • Document any sites where business need prevents disabling or upgrading.
Prepared
Confidence
medium
Sources
4

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-38512 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
3Source 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-38512Attack 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
wpstreamWpStreamwpstream, 0unaffected
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.