CVE-2025-14244: Cross Site Scripting in GreenCMS
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.
AI Analysis
Technical Summary
CVE-2025-14244 is a cross-site scripting vulnerability identified in GreenCMS version 2.3.0603, affecting the Menu Management Page component within the /Admin/Controller/CustomController.class.php file. The vulnerability stems from insufficient sanitization of the 'Link' parameter, which attackers can manipulate to inject malicious JavaScript code. This flaw allows remote attackers to craft URLs or inputs that, when processed by the vulnerable CMS, execute arbitrary scripts in the context of the victim's browser. The attack vector does not require authentication but does require user interaction, such as clicking a malicious link or visiting a compromised page. The vulnerability has a CVSS 4.8 (medium) score, reflecting moderate impact with low complexity of attack but requiring user interaction and some privileges. Notably, the affected GreenCMS version is no longer supported, meaning no official patches or updates are available, increasing exposure risk. Although no active exploitation has been reported, the public availability of exploit code heightens the threat landscape. The vulnerability primarily threatens confidentiality and integrity by enabling session hijacking, credential theft, or unauthorized actions performed under the victim's session. Availability impact is minimal. The lack of vendor support necessitates alternative mitigation strategies such as web application firewalls or manual code fixes. Organizations relying on GreenCMS 2.3.0603 should prioritize risk assessment and remediation to prevent exploitation.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily to web applications running GreenCMS 2.3.0603. Successful exploitation can lead to session hijacking, theft of sensitive user data, unauthorized actions performed on behalf of users, and potential website defacement. This can damage organizational reputation, lead to regulatory non-compliance (e.g., GDPR breaches if personal data is compromised), and disrupt business operations. Since the affected CMS version is unsupported, organizations cannot rely on vendor patches, increasing the likelihood of prolonged exposure. Attackers could leverage this vulnerability to target administrative users, amplifying the potential damage. The requirement for user interaction limits automated mass exploitation but targeted phishing or social engineering campaigns could be effective. European entities with public-facing websites using GreenCMS are at risk, especially those in sectors with high web presence such as government, education, and SMEs. The impact is compounded by the potential for lateral movement if attackers gain administrative access through XSS-facilitated session hijacking.
Mitigation Recommendations
Given the lack of official patches for GreenCMS 2.3.0603, European organizations should consider the following specific mitigations: 1) Migrate to a supported CMS platform or upgrade to a version without this vulnerability if available. 2) Implement strict input validation and output encoding on the 'Link' parameter and other user-controllable inputs to neutralize malicious scripts. 3) Deploy a web application firewall (WAF) with rules to detect and block XSS payloads targeting the vulnerable endpoint. 4) Conduct regular security audits and penetration tests focusing on web application vulnerabilities. 5) Educate users and administrators about phishing risks and safe browsing practices to reduce successful user interaction exploitation. 6) Restrict administrative access to trusted networks or via VPN to minimize exposure. 7) Monitor logs for suspicious activity related to the vulnerable component. 8) If feasible, apply manual code review and patching to sanitize inputs in the affected controller file. These steps collectively reduce the risk of exploitation despite the absence of vendor support.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Belgium, Sweden, Austria
CVE-2025-14244: Cross Site Scripting in GreenCMS
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-14244 is a cross-site scripting vulnerability identified in GreenCMS version 2.3.0603, affecting the Menu Management Page component within the /Admin/Controller/CustomController.class.php file. The vulnerability stems from insufficient sanitization of the 'Link' parameter, which attackers can manipulate to inject malicious JavaScript code. This flaw allows remote attackers to craft URLs or inputs that, when processed by the vulnerable CMS, execute arbitrary scripts in the context of the victim's browser. The attack vector does not require authentication but does require user interaction, such as clicking a malicious link or visiting a compromised page. The vulnerability has a CVSS 4.8 (medium) score, reflecting moderate impact with low complexity of attack but requiring user interaction and some privileges. Notably, the affected GreenCMS version is no longer supported, meaning no official patches or updates are available, increasing exposure risk. Although no active exploitation has been reported, the public availability of exploit code heightens the threat landscape. The vulnerability primarily threatens confidentiality and integrity by enabling session hijacking, credential theft, or unauthorized actions performed under the victim's session. Availability impact is minimal. The lack of vendor support necessitates alternative mitigation strategies such as web application firewalls or manual code fixes. Organizations relying on GreenCMS 2.3.0603 should prioritize risk assessment and remediation to prevent exploitation.
Potential Impact
For European organizations, this vulnerability poses a moderate risk primarily to web applications running GreenCMS 2.3.0603. Successful exploitation can lead to session hijacking, theft of sensitive user data, unauthorized actions performed on behalf of users, and potential website defacement. This can damage organizational reputation, lead to regulatory non-compliance (e.g., GDPR breaches if personal data is compromised), and disrupt business operations. Since the affected CMS version is unsupported, organizations cannot rely on vendor patches, increasing the likelihood of prolonged exposure. Attackers could leverage this vulnerability to target administrative users, amplifying the potential damage. The requirement for user interaction limits automated mass exploitation but targeted phishing or social engineering campaigns could be effective. European entities with public-facing websites using GreenCMS are at risk, especially those in sectors with high web presence such as government, education, and SMEs. The impact is compounded by the potential for lateral movement if attackers gain administrative access through XSS-facilitated session hijacking.
Mitigation Recommendations
Given the lack of official patches for GreenCMS 2.3.0603, European organizations should consider the following specific mitigations: 1) Migrate to a supported CMS platform or upgrade to a version without this vulnerability if available. 2) Implement strict input validation and output encoding on the 'Link' parameter and other user-controllable inputs to neutralize malicious scripts. 3) Deploy a web application firewall (WAF) with rules to detect and block XSS payloads targeting the vulnerable endpoint. 4) Conduct regular security audits and penetration tests focusing on web application vulnerabilities. 5) Educate users and administrators about phishing risks and safe browsing practices to reduce successful user interaction exploitation. 6) Restrict administrative access to trusted networks or via VPN to minimize exposure. 7) Monitor logs for suspicious activity related to the vulnerable component. 8) If feasible, apply manual code review and patching to sanitize inputs in the affected controller file. These steps collectively reduce the risk of exploitation despite the absence of vendor support.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-12-08T05:36:05.756Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6936c3245f72f49d1523dfe0
Added to database: 12/8/2025, 12:23:00 PM
Last enriched: 12/8/2025, 12:27:57 PM
Last updated: 12/10/2025, 10:23:02 PM
Views: 30
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-66473: CWE-770: Allocation of Resources Without Limits or Throttling in xwiki xwiki-platform
HighCVE-2025-65297: n/a
HighCVE-2025-65296: n/a
MediumCVE-2025-66474: CWE-95: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in xwiki xwiki-rendering
HighCVE-2025-66472: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in xwiki xwiki-platform
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.