CVE-2025-15187VulnerabilityPublished 29 Dec 2025Updated 24 Feb 2026

CVE-2025-15187: GreenCMS · Path Traversal

Affects GreenCMSSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium · end of life, no fix coming : replace or isolate GreenCMS; no fix will be released.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Dec 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-25.

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

No fix will be released: GreenCMS is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
GitHubgreencms/GreenCMS`pkg:github/greencms/GreenCMS`Other threats	Affected =2.0 =2.1 =2.2 =2.3	Fixed in–

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

AI-suggested

Since GreenCMS versions up to 2.3 are no longer supported and no official patches exist, organizations should prioritize migrating to a supported CMS platform or a maintained fork of GreenCMS if available. In the interim, administrators should restrict access to the vulnerable File Handler component by implementing strict access controls and limiting high-privilege user accounts to trusted personnel only. Web application firewalls (WAFs) can be configured to detect and block path traversal patterns in requests targeting the sqlFiles/zipFiles parameters. Conduct thorough audits of user privileges to ensure no unnecessary high-level access is granted. Additionally, isolating the GreenCMS environment within segmented network zones can reduce the risk of lateral movement if compromised. Monitoring logs for suspicious access patterns related to file handling requests can provide early detection of exploitation attempts. Employing file system permissions to restrict access to sensitive directories can mitigate the impact of successful traversal attempts. Finally, organizations should develop an incident response plan tailored to potential exploitation scenarios involving this vulnerability.

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 a 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.

Impact

The primary impact of CVE-2025-15187 is unauthorized access to files on the server hosting GreenCMS, potentially exposing sensitive configuration files, source code, or other data stored outside the web root. This can lead to information disclosure, aiding further attacks such as privilege escalation or data exfiltration. Since exploitation requires high privileges, the vulnerability is less likely to be exploited by external unauthenticated attackers but poses a significant risk if an attacker gains elevated access through other means. The lack of vendor support and patches increases the risk for organizations that continue to use affected versions, as they cannot rely on official fixes. This vulnerability could disrupt the confidentiality and integrity of data managed by GreenCMS installations, impacting organizations that rely on this CMS for their web presence or internal content management. The overall availability impact is low, as the vulnerability does not directly enable denial of service. However, exploitation could be a stepping stone for more severe attacks. Organizations worldwide using GreenCMS, especially in sectors where legacy systems persist, may face increased risk of targeted attacks leveraging this vulnerability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:36 UTC

Technical details

References

Community reviews

Related threats