CVE-2025-41396
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 · uneditedA path traversal issue exists in file uploading feature of multiple versions of PowerCMS. Arbitrary files may be overwritten by a product user.
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 confidenceA path traversal vulnerability exists in PowerCMS's file upload feature, allowing authenticated users to overwrite arbitrary files on the system by manipulating file paths during upload. The vulnerability stems from insufficient sanitization of user-supplied file paths, enabling directory traversal sequences (e.g., ../../) to escape the intended upload directory.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 installation and versionLocate PowerCMS installation files and check version number in system configuration files, typically found in version.php, config file, or admin dashboard about pageAffected if Installed version falls within >= 4.0 and < 4.61, OR >= 5.0 and < 5.31, OR >= 6.0 and < 6.71
-
Verify file upload feature is accessibleCheck if the file upload functionality is enabled in PowerCMS admin panel under Media or Upload settings, or inspect configuration files for upload-related permissionsAffected if File upload module is enabled and accessible to authenticated users
-
Confirm user authentication is in placeReview user role permissions in PowerCMS admin to determine which user roles have file upload privilegesAffected if Authenticated users (any role with upload permissions) can access the file upload feature
-
Inspect upload endpoint for path handlingExamine the file upload request handling code or proxy server logs for how file path parameters are processed - look for any path normalization or sanitization logicAffected if The upload mechanism accepts and processes user-supplied file paths without proper validation of directory traversal sequences
User is affected if PowerCMS version is 4.0-4.60, 5.0-5.30, or 6.0-6.70 AND the file upload feature is enabled for authenticated users.
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
Apply vendor patches for PowerCMS addressing path traversal in file uploads. Until patched, restrict file upload permissions to trusted users only and monitor for suspicious upload patterns containing directory traversal characters.
PowerCMS 4.61, 5.31, or 6.71 (select based on your current major version)
- 1. Backup your current PowerCMS installation including database and configuration files
- 2. Download the appropriate fixed version from the official PowerCMS vendor (www.powercms.jp) based on your current major version
- 3. For PowerCMS 4.x users: upgrade to version 4.61 or later
- 4. For PowerCMS 5.x users: upgrade to version 5.31 or later
- 5. For PowerCMS 6.x users: upgrade to version 6.71 or later
- 6. Test the file upload functionality to verify the path traversal vulnerability is remediated
- 7. Verify that uploaded files are only stored in intended directories and cannot overwrite arbitrary files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41396 — 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-41396 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