LiveActive security incident?Get immediate response
CVE Record

CVE-2025-53250: WordPress Chartbeat Plugin <= 2.0.7 - Server Side Request Forgery (SSRF) Vulnerability

Server-Side Request Forgery (SSRF) vulnerability in Chartbeat Chartbeat chartbeat allows Server Side Request Forgery.This issue affects Chartbeat: from n/a through <= 2.0.7.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-53250 is an SSRF issue in the WordPress Chartbeat plugin through version 2.0.7. A logged-in attacker could make the site initiate server-side requests, potentially exposing limited internal data or affecting request integrity. Public sources rate it medium severity, and CISA KEV status is not reported.

Executive priority

Treat as a moderate-priority WordPress plugin exposure. Prioritize internet-facing sites, sites with many authenticated users, and environments where the web server can reach sensitive internal services.

Technical view

The source bundle identifies CWE-918 SSRF in Chartbeat Chartbeat for WordPress, affecting versions through 2.0.7. CVSS 3.1 is 6.4: network exploitable, low complexity, low privileges required, no user interaction, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is most likely on WordPress sites with the Chartbeat plugin installed at version 2.0.7 or earlier. Risk depends on whether untrusted users can authenticate with sufficient plugin-accessing privileges.

Exploitation context

The provided sources do not show active exploitation, public exploit details, or KEV listing. The CVSS vector indicates exploitation requires low privileges but no user interaction, so compromise risk rises on sites with many low-trust authenticated users.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. No vulnerable endpoint, patch version, exploit maturity, or active exploitation evidence is included in the provided bundle, so validation should remain inventory- and vendor-guidance focused.

Mitigation direction

  • Check Chartbeat and Patchstack guidance for fixed versions or vendor remediation.
  • Disable or remove the plugin if it is not business-critical.
  • Restrict WordPress accounts and plugin access to trusted users only.
  • Monitor server outbound requests for unusual internal or metadata-service destinations.
  • Apply compensating egress controls where WordPress hosting supports them.

Validation and detection

  • Inventory WordPress sites for the Chartbeat plugin and installed versions.
  • Flag any Chartbeat plugin installation at version 2.0.7 or earlier.
  • Review WordPress user roles for low-trust authenticated accounts.
  • Check web and egress logs for unusual server-initiated requests.
  • Track vendor advisory updates for patch availability or mitigation details.
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-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-53250 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
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2025-53250Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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
ChartbeatChartbeatchartbeat, 0unaffected
Weakness

CWE details

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

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

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