Skip to main content

CVE-2025-5499: Deserialization in slackero phpwcms

Medium
VulnerabilityCVE-2025-5499cvecve-2025-5499
Published: Tue Jun 03 2025 (06/03/2025, 13:31:07 UTC)
Source: CVE Database V5
Vendor/Project: slackero
Product: phpwcms

Description

A vulnerability classified as critical has been found in slackero phpwcms up to 1.9.45/1.10.8. Affected is the function is_file/getimagesize of the file image_resized.php. The manipulation of the argument imgfile leads to deserialization. It is possible to launch the attack 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.

AI-Powered Analysis

AILast updated: 07/11/2025, 07:04:51 UTC

Technical Analysis

CVE-2025-5499 is a deserialization vulnerability identified in the slackero phpwcms content management system, affecting all versions up to 1.9.45 and 1.10.8. The vulnerability resides in the image_resized.php file, specifically within the is_file and getimagesize functions that process the 'imgfile' argument. An attacker can manipulate this argument to trigger unsafe deserialization of untrusted data. Deserialization vulnerabilities occur when untrusted input is deserialized without proper validation, potentially allowing attackers to execute arbitrary code, escalate privileges, or cause denial of service. This vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 base score is 6.9 (medium severity), reflecting network attack vector, low complexity, no privileges or user interaction needed, and limited impact on confidentiality, integrity, and availability. Although no known exploits are currently observed in the wild, the public disclosure of the exploit code increases the likelihood of exploitation attempts. The vendor has addressed the issue in versions 1.9.46 and 1.10.9, and upgrading to these or later versions is recommended to mitigate the risk. Organizations using affected phpwcms versions should prioritize patching to prevent potential compromise through this vulnerability.

Potential Impact

For European organizations, the impact of CVE-2025-5499 can be significant depending on the deployment scale of phpwcms. Successful exploitation could allow remote attackers to execute arbitrary code on web servers hosting phpwcms, leading to unauthorized access, data breaches, defacement, or disruption of web services. This can compromise the confidentiality and integrity of sensitive information managed via the CMS, including customer data, internal documents, or intellectual property. Availability may also be affected if attackers leverage the vulnerability to cause denial of service or persistent backdoors. Given phpwcms is a web content management system, organizations in sectors such as government, education, media, and small to medium enterprises that rely on it for their web presence are at risk. The lack of authentication requirement and remote exploitability heighten the threat, especially for publicly accessible web servers. Additionally, the public exploit disclosure increases the urgency for European entities to address this vulnerability promptly to avoid potential targeted attacks or opportunistic exploitation.

Mitigation Recommendations

1. Immediate upgrade of phpwcms installations to versions 1.9.46 or 1.10.9 or later, as these contain patches that fix the deserialization vulnerability. 2. If immediate upgrade is not feasible, implement web application firewall (WAF) rules to detect and block malicious payloads targeting the 'imgfile' parameter, focusing on patterns indicative of serialized data or unusual input. 3. Restrict access to the image_resized.php endpoint via network segmentation or IP whitelisting where possible, limiting exposure to trusted sources only. 4. Conduct thorough code review and harden input validation on all parameters that accept user input, especially those involved in file handling or deserialization processes. 5. Monitor web server logs and intrusion detection systems for suspicious activity related to deserialization attempts or unusual requests to the vulnerable functions. 6. Employ runtime application self-protection (RASP) tools if available to detect and prevent exploitation attempts in real time. 7. Educate development and security teams about the risks of insecure deserialization and best practices for secure coding to prevent similar vulnerabilities in the future.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-06-03T05:14:53.909Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 683eff8d182aa0cae27db846

Added to database: 6/3/2025, 1:58:37 PM

Last enriched: 7/11/2025, 7:04:51 AM

Last updated: 8/2/2025, 8:25:51 PM

Views: 14

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats