dbcve.org
PowercmsApplication · Alfasado

CVE-2025-46359

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

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
A path traversal issue exists in backup and restore feature of multiple versions of PowerCMS. A product administrator may execute arbitrary code by restoring a crafted backup file.

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

A path traversal vulnerability exists in the backup and restore feature of PowerCMS. An authenticated product administrator can restore a crafted backup file containing path traversal sequences (e.g., ../../../') to write files to arbitrary locations on the server, leading to arbitrary code execution.

MitigationImplement strict path validation and sanitization for all files within backup archives before extraction; use allowlist-based validation to ensure extracted paths remain within intended directories; restrict backup/restore functionality to minimum necessary administrators.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 installation version
    Locate the version file or admin dashboard that displays the PowerCMS version number. Common locations include: version file in the installation directory, footer of admin pages, or system information panel.
    Affected if The installed version is >= 4.0 and < 4.61, OR >= 5.0 and < 5.31, OR >= 6.0 and < 6.71
  2. Confirm backup and restore feature is enabled
    Access the admin panel and navigate to the backup/restore section, typically found under System Settings, Maintenance, or Tools. Check if the backup and restore functionality is present and accessible.
    Affected if The backup/restore feature is enabled and accessible in the admin interface
  3. Verify administrator account access
    Check if any user accounts with administrator-level privileges exist in the system. This vulnerability requires an authenticated product administrator.
    Affected if There are active administrator accounts with access to the backup/restore functionality
  4. Examine backup archive handling
    If backup archives exist, inspect the extraction process for path traversal protections. This typically requires code review or testing with a crafted archive containing ../ sequences.
    Affected if The system does not validate or sanitize paths within backup archives before extraction, allowing ../ sequences to traverse outside the intended directory

The environment is affected if PowerCMS version falls within 4.0-4.60, 5.0-5.30, or 6.0-6.70 AND the backup/restore feature is enabled with administrator access available.

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 path validation and sanitization for all files within backup archives before extraction; use allowlist-based validation to ensure extracted paths remain within intended directories; restrict backup/restore functionality to minimum necessary administrators.

Recommended fix High confidence

PowerCMS 4.61 (for 4.x branch), 5.31 (for 5.x branch), or 6.71 (for 6.x branch) - upgrade to the latest stable release in your current branch

  1. 1. Identify your current PowerCMS version by checking the administration interface or version file
  2. 2. Determine which version branch you are on (4.x, 5.x, or 6.x)
  3. 3. Download the appropriate fixed version from the official PowerCMS distribution (www.powercms.jp) - for 4.x use 4.61+, for 5.x use 5.31+, for 6.x use 6.71+
  4. 4. Create a complete backup of the current PowerCMS installation including database and files
  5. 5. Review the official upgrade documentation from PowerCMS before proceeding
  6. 6. Apply the upgrade following the standard upgrade procedure for your version branch
  7. 7. Verify the upgrade was successful by checking the version in the admin interface
  8. 8. Test the backup and restore functionality to confirm the vulnerability is resolved
Caveat Review release notes for your version branch as minor version upgrades typically have minimal breaking changes; ensure custom templates/plugins are compatible with the new version

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-46359 — 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-46359 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