LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54673: WordPress Chartify plugin <= 3.5.3 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Ays Pro Chartify chart-builder allows Cross Site Request Forgery.This issue affects Chartify: from n/a through <= 3.5.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-54673 is a CSRF issue in the WordPress Chartify chart-builder plugin through version 3.5.3. A victim with relevant site privileges may need to be tricked into interacting with a malicious page. The reported impact is limited integrity loss, not data theft or service outage.

Executive priority

Treat this as a moderate-priority WordPress plugin hygiene issue. It is not currently supported as actively exploited, but vulnerable public WordPress admin surfaces can create business risk if administrators are targeted by social engineering.

Technical view

The source bundle identifies CWE-352 Cross-Site Request Forgery in Ays Pro Chartify chart-builder, affecting versions through 3.5.3. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges required by the attacker, and required user interaction. No confidentiality or availability impact is reported.

Likely exposure

Exposure is likely limited to WordPress sites running the Chartify chart-builder plugin at version 3.5.3 or earlier. The bundle does not identify other affected products, hosted services, or confirmed default configurations.

Exploitation context

The bundle does not report active exploitation, and KEV status is false. Exploitation would require user interaction, consistent with CSRF, and the known impact is low integrity change. No public exploit details are included in the provided sources.

Researcher notes

Evidence is limited to CVE and Patchstack-style vulnerability metadata. The affected-version statement says through <= 3.5.3, while the structured affected record is sparse. No fixed version, proof of exploitation, or detailed vulnerable action is provided in the bundle.

Mitigation direction

  • Inventory WordPress sites for the Chartify chart-builder plugin.
  • Check installed Chartify versions and prioritize versions 3.5.3 or earlier.
  • Review vendor or Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin when a vendor-supported fixed version is available.
  • Disable or remove the plugin where it is not business-critical.

Validation and detection

  • Confirm whether Chartify chart-builder is installed on each WordPress site.
  • Record the installed plugin version and compare it with <= 3.5.3.
  • Review admin activity for unexpected Chartify configuration or chart changes.
  • Verify remediation against vendor or Patchstack guidance after updating or disabling.
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-2025-54673 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-2025-54673Attack 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
Ays ProChartifychart-builder, 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.