Cyber Resilience

CVE-2025-54752

Alfasado Powercms 4.0 – 4.61

Published
31 July 2025
Modified
17 June 2026
CVSS Score v4 4.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0024 15th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-54752 is a medium-severity Improper Neutralization of Formula Elements in a CSV File (CWE-1236) vulnerability in Alfasado Powercms. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-15 (Information Output Filtering) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Multiple versions of PowerCMS improperly neutralize formula elements in a CSV file. If a product user creates a malformed entry and a victim user downloads it as a CSV file and opens it in the user's environment, the embedded code…

more

may be executed.

CWE(s)
CWE-1236

Related Threats

MITRE ATT&CK Enterprise Techniques

T1204 User Execution Execution
An adversary may rely upon specific actions by a user in order to gain execution.
attack.mitre.org →
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
attack.mitre.org →
T1566 Phishing Initial Access
Adversaries may send phishing messages to gain access to victim systems.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-50297Same product: Alfasado Powercms
CVE-2025-41391Same product: Alfasado Powercms
CVE-2023-49117Same product: Alfasado Powercms
CVE-2025-41396Same product: Alfasado Powercms
CVE-2025-54757Same product: Alfasado Powercms
CVE-2025-46359Same product: Alfasado Powercms
CVE-2025-36563Same product: Alfasado Powercms
CVE-2024-45084Shared CWE-1236
CVE-2024-47485Shared CWE-1236
CVE-2026-23873Shared CWE-1236

Affected Assets

alfasado
powercms
4.0 — 4.61 · 5.0 — 5.31 · 6.0 — 6.71

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10

Mitigating Controls (NIST 800-53 r5) AI

SI-15 Information Output Filtering good match

Output filtering/validation directly stops unneutralized formula elements from being written into CSV files.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require output neutralization for untrusted CSV content to block formula injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect formula injection but does not itself implement the mitigation.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and output encoding that directly prevents formula injection in CSV exports.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for safe CSV generation and handling of untrusted data.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage safe data export design but do not specifically address CSV formula neutralization.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require neutralization of special characters when writing CSV files.

References