VulnerabilityPublished 8 Dec 2025Updated 24 Feb 2026

CVE-2025-14244: GreenCMS · Cross-site Scripting

Affects GreenCMSSource CVE Database V5

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

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: 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: 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: None: There is no impact to availability within 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 8 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 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

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.3.0603	Fixed in–

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

AI-suggested

Given the lack of official patches due to the product's unsupported status, organizations should prioritize upgrading to a supported and patched version of GreenCMS or migrating to an alternative CMS platform. If upgrading is not immediately feasible, implement strict input validation and output encoding on the 'Link' parameter within the Menu Management Page to neutralize malicious scripts. Employ web application firewalls (WAFs) with custom rules to detect and block XSS payloads targeting this specific parameter. Restrict administrative access to trusted networks and enforce multi-factor authentication to reduce the risk of compromised credentials. Conduct regular security awareness training for administrators to recognize and avoid phishing or social engineering attempts that could trigger user interaction-based exploits. Monitor logs for suspicious activities related to the Menu Management Page and the 'Link' parameter. Finally, isolate legacy CMS installations from critical infrastructure and sensitive data to limit potential damage.

Description

A flaw has been found in GreenCMS 2.3.0603. Affected by this issue is some unknown functionality of the file /Admin/Controller/CustomController.class.php of the component Menu Management Page. This manipulation of the argument Link causes cross site scripting. The attack may be initiated remotely. The exploit has been published and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Impact

The primary impact of this vulnerability is the potential for attackers to execute malicious scripts in the context of authenticated users with high privileges, such as administrators. This can lead to session hijacking, credential theft, unauthorized actions within the CMS, or defacement of the website. Since the vulnerability affects an unsupported version of GreenCMS, organizations using it face increased risk due to the absence of official patches or vendor support. The attack requires user interaction and high privileges, limiting the scope somewhat; however, successful exploitation can compromise the integrity and confidentiality of the CMS environment. This can disrupt website management, damage organizational reputation, and potentially expose sensitive data managed through the CMS. The lack of availability impact means the system remains operational, but the trustworthiness of the content and administrative control is undermined.

Summary

CVE-2025-14244 identifies a cross-site scripting vulnerability in GreenCMS version 2.3.0603, specifically within the /Admin/Controller/CustomController.class.php file that handles the Menu Management Page. The vulnerability is caused by insufficient input validation or sanitization of the 'Link' parameter, which can be manipulated by an attacker to inject malicious JavaScript code. This flaw allows remote attackers to execute arbitrary scripts in the context of an authenticated administrator or user with high privileges. The vulnerability does not require authentication bypass but does require the attacker to have high privileges (PR:H) and some user interaction (UI:P), such as tricking an administrator into clicking a crafted link. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no confidentiality impact (C:N), low integrity impact (I:L), and no availability impact (A:N). The vulnerability affects only an unsupported version of GreenCMS, and no official patches or updates have been released. While no known exploits are currently active in the wild, proof-of-concept code has been published, increasing the risk of future exploitation. The vulnerability primarily threatens the confidentiality and integrity of administrative sessions and data within the affected CMS installation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats