CVE-2025-54752
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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 may be executed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a CSV formula injection vulnerability in PowerCMS. The application fails to neutralize special characters (such as =, +, -, @) that spreadsheet software interprets as formula directives when exporting data to CSV format. An attacker who can control data imported into the system can embed malicious formulas that execute arbitrary commands on the victim's workstation when they open the downloaded CSV in Excel or similar software.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0, < 4.61>= 5.0, < 5.31>= 6.0, < 6.71CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PowerCMS versionLocate the PowerCMS installation directory and check the version file or configuration. Common locations include a version.php, version.txt, or the admin dashboard showing the software version.Affected if The installed version falls within >= 4.0, < 4.61 OR >= 5.0, < 5.31 OR >= 6.0, < 6.71, indicating the vulnerable version range.
-
Locate CSV export functionalitySearch the PowerCMS codebase for CSV export routines. Look for functions handling data export to CSV format, typically in export, download, or reporting modules.Affected if CSV export functionality exists and is accessible to users who can import or input data into the system.
-
Inspect CSV export code for formula character handlingExamine the CSV generation code that handles exported data fields. Look for sanitization logic that prefixes special characters (=, +, -, @) with a single quote or applies escaping before writing to CSV.Affected if The CSV export code does NOT neutralize formula characters (=, +, -, @) in user-supplied data before writing to the CSV file.
-
Test exported CSV for formula injectionImport a test record containing a field value starting with = (e.g., =1+2) into the CMS, then export that data to CSV and open the resulting file in a text editor to inspect the raw content.Affected if The exported CSV contains unescaped formula characters at the beginning of fields, allowing spreadsheet software to interpret them as formulas.
-
Review server logs for CSV download activityExamine web server access logs for requests to CSV export endpoints, noting the user and timestamp of exports.Affected if Exports are occurring and may contain untrusted user data that could have been weaponized.
You are affected if your PowerCMS version is within the vulnerable ranges AND CSV export functionality exists without proper sanitization of formula characters in user-controlled data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.615.316.71
PowerCMS should implement output encoding for CSV exports by prefixing formula characters with a single quote or escaping them, and by applying context-aware sanitization to all user-supplied data before CSV generation. Users should open CSV files in text editors first before viewing in spreadsheets.
PowerCMS 4.61 (for 4.x), 5.31 (for 5.x), or 6.71 (for 6.x) - choose the corresponding version for your current branch
- Identify the currently installed PowerCMS version through the admin interface or system files
- For PowerCMS 4.x branch: upgrade to version 4.61 or later
- For PowerCMS 5.x branch: upgrade to version 5.31 or later
- For PowerCMS 6.x branch: upgrade to version 6.71 or later
- Download the appropriate fixed version from the official vendor (www.powercms.jp)
- Backup the current installation and database before upgrading
- Apply the upgrade following the vendor's documented upgrade procedure
- Verify the upgrade was successful by checking the version in the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54752 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data