dbcve.org
PowercmsApplication · Alfasado

CVE-2025-41391

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 4.61 / 5.31 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Stored cross-site scripting vulnerability exists in multiple versions of PowerCMS. If a product user accesses a malicious page, 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

Stored cross-site scripting (XSS) vulnerability in PowerCMS allows attackers to inject malicious scripts that are persisted on the server and executed when users access affected pages. The medium severity (CVSS 5.4) suggests limited scope or some user interaction is required for exploitation.

MitigationImplement input validation and output encoding for all user-supplied content rendered in the application. Update PowerCMS to the latest patched version if available.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify PowerCMS version
    Locate the PowerCMS installation directory and check for a version file, typically named 'version.php', 'VERSION', or accessible through the admin dashboard under System > Information or similar. Alternatively, inspect the mt-config.cgi file for version indicators or check the application's meta information.
    Affected if The installed version falls within >= 4.0, < 4.61 OR >= 5.0, < 5.31 OR >= 6.0, < 6.71
  2. Determine if user-generated content modules are active
    Review the PowerCMS admin panel to identify enabled plugins or modules that accept user submissions, such as comment systems, user profiles, blogs, forums, or custom fields. Check the mt-config.cgi or database for active component settings.
    Affected if Any module that accepts and stores user-supplied input is enabled and publicly accessible
  3. Inspect stored content for script injection
    Query the database tables that store user-generated content (commonly mt_comment, mt_entry, or custom object tables) for suspicious patterns such as <script>, javascript:, onerror=, onload=, or other HTML event handlers. Use database tools or the admin interface to review recent submissions.
    Affected if Any records contain unsanitized HTML or JavaScript code in fields that should only contain plain text

A user is affected if PowerCMS is installed at a version within the affected ranges AND publicly accessible user input modules are enabled that accept and display stored content without proper sanitization.

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 input validation and output encoding for all user-supplied content rendered in the application. Update PowerCMS to the latest patched version if available.

Recommended fix High confidence

PowerCMS 4.61, 5.31, or 6.71 (depending on your current major version branch)

  1. 1. Identify the current PowerCMS version by checking the admin dashboard or version file
  2. 2. Determine the appropriate upgrade path based on current version: if 4.x upgrade to 4.61, if 5.x upgrade to 5.31, if 6.x upgrade to 6.71
  3. 3. Create a complete backup of the PowerCMS database and files
  4. 4. Download the fixed version from the official PowerCMS website (www.powercms.jp)
  5. 5. Follow the standard PowerCMS upgrade procedure documented in the official manual
  6. 6. After upgrade, verify the version number reflects the fixed release
  7. 7. Test that the application functions correctly after the upgrade
Caveat Review the release notes for the specific version to check for any backward-incompatible changes or required migration steps

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

Fix this in Powercms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41391 — 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-41391 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