CVE-2025-41396VulnerabilityPublished 31 Jul 2025

CVE-2025-41396: Alfasado PowerCMS · Path Traversal

Affects Alfasado PowerCMSSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

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

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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 26 Oct 2026.

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

Organizations should immediately verify if they are running PowerCMS version 6.7 or earlier and prioritize upgrading to a fixed version once available from Alfasado Inc. In the absence of an official patch, administrators should implement strict input validation and sanitization on file upload paths to prevent directory traversal sequences (e.g., '..' or absolute paths). Employing web application firewalls (WAFs) with custom rules to detect and block suspicious file upload requests can provide interim protection. Restricting file system permissions so that the CMS process can only write to designated upload directories will limit the potential damage from exploitation. Regularly auditing file integrity and monitoring logs for unusual file modification activities can help detect exploitation attempts early. Additionally, isolating the CMS environment using containerization or sandboxing techniques can reduce the blast radius of a successful attack. Finally, educating users about the risks and ensuring that only trusted users have upload privileges will reduce the likelihood of exploitation.

Description

A path traversal issue exists in file uploading feature of multiple versions of PowerCMS. Arbitrary files may be overwritten by a product user.

Impact

For European organizations using PowerCMS 6.x or earlier versions, this vulnerability poses a tangible risk to the integrity and availability of their content management systems. Since PowerCMS is often used to manage web content, exploitation could disrupt website operations, leading to service outages or defacement. Overwritten files might include CMS core files or server configuration files, potentially allowing attackers to escalate privileges or cause persistent disruptions. The impact is particularly significant for organizations that rely on PowerCMS for public-facing websites or internal portals, as service interruptions could affect customer trust, business continuity, and compliance with data availability requirements under regulations like GDPR. Additionally, if the overwritten files include scripts or executables, there is a risk of further compromise or lateral movement within the network. Although confidentiality is not directly impacted, the integrity and availability concerns are sufficient to warrant prompt attention, especially in sectors such as government, finance, healthcare, and media where CMS uptime and data integrity are critical.

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