Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-15187: Path Traversal in GreenCMS

0
Medium
VulnerabilityCVE-2025-15187cvecve-2025-15187
Published: Mon Dec 29 2025 (12/29/2025, 12:02:08 UTC)
Source: CVE Database V5
Product: GreenCMS

Description

A vulnerability was found in GreenCMS up to 2.3. This affects an unknown part of the file /DataController.class.php of the component File Handler. Performing manipulation of the argument sqlFiles/zipFiles results in path traversal. The attack can be initiated remotely. The exploit has been made public and could be used. This vulnerability only affects products that are no longer supported by the maintainer.

AI-Powered Analysis

AILast updated: 12/30/2025, 23:54:01 UTC

Technical Analysis

CVE-2025-15187 is a path traversal vulnerability identified in GreenCMS, a content management system, affecting versions 2.0 through 2.3. The flaw exists in the File Handler component, specifically in the /DataController.class.php file, where the arguments sqlFiles and zipFiles are not properly sanitized. This improper input validation allows an attacker to manipulate these parameters to perform directory traversal attacks, potentially accessing files outside the intended directory scope. The vulnerability can be exploited remotely but requires the attacker to have high-level privileges (authenticated with high rights) on the system. No user interaction is needed, and the vulnerability affects confidentiality and integrity by enabling unauthorized file access or modification. The vulnerability has a CVSS 4.0 base score of 5.1, classified as medium severity, reflecting moderate impact and exploitation complexity. Importantly, GreenCMS versions affected are no longer supported by the vendor, and no official patches have been released, increasing the risk for organizations that continue to use these legacy versions. Although the exploit code has been publicly disclosed, there are no confirmed reports of active exploitation in the wild. The lack of vendor support means organizations must rely on alternative mitigation strategies or upgrade paths. This vulnerability highlights the risks associated with using unsupported software and the critical need for timely patching or migration to supported platforms.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to those still operating legacy GreenCMS installations. Successful exploitation could lead to unauthorized disclosure or modification of sensitive files, impacting confidentiality and integrity of data managed by the CMS. This could include exposure of configuration files, user data, or other critical assets stored on the server. Since exploitation requires high privilege authentication, the threat is somewhat limited to insiders or attackers who have already compromised credentials. However, given the lack of vendor support and patches, the risk of prolonged exposure is significant. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, could face compliance issues if sensitive data is exposed. Additionally, the public availability of exploit code increases the likelihood of opportunistic attacks, especially in environments where legacy CMS platforms are still in use. The vulnerability does not directly affect availability but could be leveraged as part of a broader attack chain. European entities relying on GreenCMS should prioritize risk assessments and remediation to prevent potential data breaches or integrity violations.

Mitigation Recommendations

Since no official patches are available due to the product being unsupported, European organizations should consider the following specific mitigation steps: 1) Immediately audit all GreenCMS instances to identify affected versions (2.0 to 2.3) and isolate them from public networks if possible. 2) Restrict access to the CMS administration interfaces to trusted internal networks and enforce strong authentication and authorization controls to minimize the risk of high privilege compromise. 3) Implement web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting sqlFiles and zipFiles parameters. 4) Conduct thorough credential audits and enforce multi-factor authentication (MFA) for all CMS users with elevated privileges. 5) Where feasible, migrate to a supported CMS platform or upgrade to a version not affected by this vulnerability. 6) Monitor logs for suspicious access patterns or attempts to exploit path traversal vectors. 7) Employ file integrity monitoring on critical CMS directories to detect unauthorized changes. 8) Educate administrators about the risks of using unsupported software and the importance of timely updates. These measures collectively reduce the attack surface and mitigate the risk until a full migration or replacement can be completed.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-28T08:37:30.252Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 695450bfdb813ff03e2bfc27

Added to database: 12/30/2025, 10:22:55 PM

Last enriched: 12/30/2025, 11:54:01 PM

Last updated: 2/7/2026, 7:39:52 AM

Views: 34

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats