dbcve.org
PowercmsApplication · Alfasado

CVE-2025-54757

HIGH · 8.0 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 4.61 / 5.31 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 · unedited
Multiple versions of PowerCMS allow unrestricted upload of dangerous files. If a product administrator accesses a malicious file uploaded by a product user, an arbitrary script may be executed on the browser.

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 confidence

PowerCMS multiple versions allow unrestricted upload of dangerous files. When a product administrator accesses a malicious file uploaded by a user, arbitrary scripts can execute in the administrator's browser - indicating a stored XSS vulnerability via file upload.

MitigationImplement strict allowlist-based file type validation server-side, sanitize filenames, store files outside webroot or with non-executable headers, and restrict admin access to uploaded content.

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
PowercmsApplication
Affected:>= 4.0, < 4.61>= 5.0, < 5.31>= 6.0, < 6.71

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify PowerCMS version
    Locate the version file or admin dashboard 'System Information' page in your PowerCMS installation. Common paths include /mt-static/index.html, a config file, or the admin interface system settings.
    Affected if The installed version falls within 4.0 to 4.60, 5.0 to 5.30, or 6.0 to 6.70 (the vulnerable version ranges).
  2. Verify file upload feature is enabled
    Check your PowerCMS admin panel under 'System Settings' or 'Website Settings' for the file upload or asset upload functionality. Look for configuration options related to uploading files, images, or attachments.
    Affected if File upload is enabled and users can submit files to the system.
  3. Check uploaded file storage location
    Examine the file upload configuration or inspect the directory where uploaded files are stored (commonly /mt-static/uploads/, /cgi-bin/, or a configurable asset path). Determine if this directory is within the web server's document root.
    Affected if Uploaded files are stored in a web-accessible directory (webroot or subdirectory) where they can be directly accessed via URL.
  4. Inspect file type validation mechanism
    Review the server-side file upload handling code or admin configuration for allowlist-based file type validation. Check if there's any server-side validation that restricts file types before processing.
    Affected if There is no server-side allowlist validation, or the validation can be bypassed (for example, if it relies solely on client-side checks or file extension renaming).

Your environment is affected if you are running a vulnerable PowerCMS version (4.x before 4.61, 5.x before 5.31, or 6.x before 6.71) with the file upload feature enabled and uploaded files are stored in a web-accessible location without strict server-side allowlist validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.61 / 5.31 / 6.71 or later
Fixed in 4.615.316.71
Interim mitigation

Implement strict allowlist-based file type validation server-side, sanitize filenames, store files outside webroot or with non-executable headers, and restrict admin access to uploaded content.

Recommended fix Moderate confidence

Upgrade to PowerCMS 4.61 (for v4.x), 5.31 (for v5.x), or 6.71 (for v6.x)

  1. 1. Back up your current PowerCMS database and all files
  2. 2. Download PowerCMS version 4.61 (if currently on major version 4), version 5.31 (if on major version 5), or version 6.71 (if on major version 6) from the official vendor site (www.powercms.jp)
  3. 3. Review the vendor's upgrade instructions specific to your version
  4. 4. Test the upgrade in a staging environment before deploying to production
  5. 5. Deploy the upgrade to production environment
  6. 6. Verify the installation and test file upload functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powercms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54757 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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