CVE-2025-41391VulnerabilityPublished 31 Jul 2025

CVE-2025-41391: Alfasado PowerCMS · Cross-site scripting (XSS)

Affects Alfasado PowerCMSSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediate review and restriction of user privileges within PowerCMS to the minimum necessary, especially for users who can input content that is rendered to others. 2. Implement strict input validation and output encoding on all user-supplied content within PowerCMS to prevent injection of malicious scripts. 3. Monitor and audit CMS content for suspicious or unexpected scripts or HTML elements that could indicate exploitation attempts. 4. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the CMS-managed sites. 5. Educate CMS users about the risks of clicking on untrusted links or accessing unknown pages to reduce the risk of user interaction exploitation. 6. Stay updated with Alfasado Inc. announcements for official patches or updates addressing CVE-2025-41391 and apply them promptly once available. 7. Consider deploying web application firewalls (WAF) with rules tailored to detect and block XSS payloads targeting PowerCMS. 8. Conduct penetration testing focused on XSS vulnerabilities within PowerCMS environments to identify and remediate weaknesses proactively.

Description

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.

Impact

For European organizations using PowerCMS 6.7 or earlier, this vulnerability poses a moderate risk. The confidentiality and integrity of user sessions and data could be compromised if attackers successfully inject malicious scripts. This could lead to unauthorized access to sensitive information, session hijacking, or manipulation of content. Organizations in sectors such as government, finance, healthcare, and media that rely on PowerCMS for content management may face reputational damage, regulatory penalties under GDPR for data breaches, and operational disruptions. Since the vulnerability requires some level of user privileges and interaction, internal users or contributors with access to the CMS could be targeted to inject malicious scripts, which then affect other users including administrators. The scope change indicates that the impact could extend beyond the immediate CMS component, potentially affecting integrated systems or services. Although no exploits are currently known in the wild, the public disclosure increases the risk of exploitation attempts, especially if patches are delayed. European organizations with public-facing websites or intranet portals managed by PowerCMS should be particularly vigilant, as attackers could leverage this vulnerability to conduct phishing, spread malware, or escalate privileges within the network.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 31 Jul 2025, 08:03 UTC

Technical details

References

Community reviews

Related threats