dbcve.org
PowercmsApplication · Alfasado

CVE-2025-36563

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 4.61 / 5.31 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Reflected cross-site scripting vulnerability exists in multiple versions of PowerCMS. If a product administrator accesses a crafted URL, 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

A reflected cross-site scripting (XSS) vulnerability exists in multiple versions of PowerCMS. The vulnerability allows an attacker to inject malicious JavaScript code into a URL that, when clicked by a product administrator, executes in their browser within the context of the application, potentially enabling session hijacking or credential theft.

MitigationApply vendor-supplied patches for PowerCMS to implement proper input validation and output encoding on all user-supplied parameters. Until patched, administrators should avoid clicking untrusted URLs.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm PowerCMS installation
    Locate the PowerCMS installation by checking for its typical directory structure or by accessing the application's login/admin page in your browser. PowerCMS typically presents an admin login page at a path like /mt-admin/ or similar administrator endpoints.
    Affected if PowerCMS is present in your environment
  2. Identify installed PowerCMS version
    Access the administrator dashboard or check version information in the CMS configuration. In PowerCMS, version information is often displayed in the admin footer, system information page, or can be found in a VERSION or version file within the installation directory.
    Affected if You cannot determine the version or the version falls outside the known safe ranges
  3. Compare version against affected ranges
    Review the detected version against the affected ranges: 4.0 through 4.60.x, 5.0 through 5.30.x, and 6.0 through 6.70.x.
    Affected if Your installed version is 4.0 <= version < 4.61 OR 5.0 <= version < 5.31 OR 6.0 <= version < 6.71
  4. Verify web administrator interface is accessible
    Confirm that the PowerCMS administrator interface is reachable over the network. Attempt to access the admin login page via HTTP/HTTPS from a browser or curl request.
    Affected if The admin interface is exposed and your version falls within the affected ranges listed above

You are affected if PowerCMS is installed and the installed version falls within 4.0 to 4.60.x, 5.0 to 5.30.x, or 6.0 to 6.70.x, with the admin interface accessible over the network.

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

Apply vendor-supplied patches for PowerCMS to implement proper input validation and output encoding on all user-supplied parameters. Until patched, administrators should avoid clicking untrusted URLs.

Recommended fix Moderate confidence

PowerCMS 4.61+ (4.x branch), 5.31+ (5.x branch), or 6.71+ (6.x branch) depending on your current branch

  1. 1. Identify the current PowerCMS version in use by checking the admin panel or configuration files.
  2. 2. Determine which branch (4.x, 5.x, or 6.x) the installation belongs to.
  3. 3. For PowerCMS 4.x branches: upgrade to version 4.61 or later.
  4. 4. For PowerCMS 5.x branches: upgrade to version 5.31 or later.
  5. 5. For PowerCMS 6.x branches: upgrade to version 6.71 or later.
  6. 6. After upgrading, verify the admin panel is accessible and functioning correctly.
  7. 7. Test that the XSS vulnerability is no longer present by attempting to reproduce the reflected XSS with the previously vulnerable URL parameters.
Caveat Review release notes for any breaking changes between your current version and the target upgrade version before proceeding

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

Fix this in Powercms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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