CVE-2025-5498VulnerabilityPublished 3 Jun 2025

CVE-2025-5498: slackero phpwcms · Deserialization

Affects slackero phpwcmsSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system 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 Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 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

Affected software

Product	Affected	Fixed in
GitHubslackero/phpwcms`pkg:github/slackero/phpwcms`Other threats	Affected =1.9.0 =1.9.1 =1.9.2 =1.9.3 =1.9.4 =1.9.5 =1.9.6 =1.9.7 =1.9.8 =1.9.9 =1.9.10 =1.9.11 =1.9.12 =1.9.13 =1.9.14 =1.9.15 =1.9.16 =1.9.17 =1.9.18 =1.9.19 =1.9.20 =1.9.21 =1.9.22 =1.9.23 =1.9.24 =1.9.25 =1.9.26 =1.9.27 =1.9.28 =1.9.29 =1.9.30 =1.9.31 =1.9.32 =1.9.33 =1.9.34 =1.9.35 =1.9.36 =1.9.37 =1.9.38 =1.9.39 =1.9.40 =1.9.41 =1.9.42 =1.9.43 =1.9.44 =1.9.45 =1.10.0 =1.10.1 =1.10.2 =1.10.3 =1.10.4 =1.10.5 =1.10.6 =1.10.7 =1.10.8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Beyond upgrading to phpwcms versions 1.9.46 or 1.10.9, organizations should implement several practical measures: 1) Conduct a thorough inventory of phpwcms instances to identify affected versions. 2) Apply strict input validation and sanitization on all user-supplied parameters, especially those related to 'cpage_custom', to prevent malicious payloads from reaching deserialization routines. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious deserialization patterns or anomalous requests targeting the vulnerable endpoint. 4) Monitor logs for unusual activity related to the Custom Source Tab component and file_get_contents/is_file function calls. 5) Restrict access to the vulnerable component by IP whitelisting or network segmentation where feasible. 6) Implement runtime application self-protection (RASP) solutions to detect and prevent exploitation attempts in real time. 7) Educate development and security teams about secure deserialization practices to avoid similar vulnerabilities in custom code.

Description

A vulnerability was found in slackero phpwcms up to 1.9.45/1.10.8. It has been rated as critical. This issue affects the function file_get_contents/is_file of the file include/inc_lib/content/cnt21.readform.inc.php of the component Custom Source Tab. The manipulation of the argument cpage_custom leads to deserialization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.9.46 and 1.10.9 is able to address this issue. It is recommended to upgrade the affected component.

Impact

For European organizations using slackero phpwcms, this vulnerability poses a moderate risk. Exploitation could lead to unauthorized code execution or manipulation of content management functions, potentially compromising website integrity and availability. While the confidentiality impact is low, attackers could deface websites, inject malicious content, or disrupt services, affecting business reputation and user trust. Organizations in sectors relying heavily on web presence, such as e-commerce, media, and government services, may experience operational disruptions. The medium severity and requirement for user interaction somewhat limit the threat scope; however, the remote exploitability and public availability of the exploit code increase the urgency for mitigation. Failure to patch could lead to targeted attacks exploiting this vulnerability, especially in environments where phpwcms is used without additional security controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 07:04 UTC

Technical details

References

Community reviews

Related threats