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-67290: n/a

0
Medium
VulnerabilityCVE-2025-67290cvecve-2025-67290
Published: Mon Dec 22 2025 (12/22/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

A stored cross-site scripting (XSS) vulnerability in the Page Settings module of Piranha CMS v12.1 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Excerpt field.

AI-Powered Analysis

AILast updated: 12/22/2025, 20:30:35 UTC

Technical Analysis

CVE-2025-67290 is a stored cross-site scripting vulnerability identified in the Page Settings module of Piranha CMS version 12.1. The vulnerability arises because the Excerpt field does not properly sanitize or encode user input, allowing attackers to inject crafted payloads containing malicious JavaScript or HTML code. When these payloads are stored and later rendered in the web interface, they execute in the browsers of users who view the affected content. Stored XSS is particularly dangerous because the malicious code persists on the server and can affect multiple users without requiring repeated attacker interaction. Exploitation could lead to session hijacking, credential theft, unauthorized actions performed on behalf of users, or distribution of malware. Although no CVSS score has been assigned and no public exploits are currently known, the vulnerability is publicly disclosed and should be treated seriously. The lack of patch links suggests that a fix may not yet be available, increasing the urgency for organizations to implement interim mitigations. The vulnerability specifically impacts Piranha CMS installations that use the Page Settings module and allow input into the Excerpt field, which is common in content management scenarios. Attackers with the ability to submit or modify content in this field can exploit this vulnerability without requiring authentication if the CMS allows public submissions, or with limited privileges if restricted to authenticated users. The vulnerability affects confidentiality, integrity, and potentially availability if exploited to perform further attacks. Given the widespread use of CMS platforms in Europe for websites and intranets, this vulnerability poses a significant risk to organizations relying on Piranha CMS.

Potential Impact

For European organizations, exploitation of this stored XSS vulnerability could lead to significant security incidents including theft of user credentials, session hijacking, and unauthorized actions performed on behalf of users. This can result in data breaches, defacement of websites, loss of customer trust, and regulatory penalties under GDPR if personal data is compromised. Organizations operating critical web services or handling sensitive user data are at higher risk. The persistence of the malicious payload increases the attack surface and potential damage. Additionally, attackers could leverage this vulnerability as a foothold for further attacks within the network. The impact is amplified in sectors such as finance, healthcare, government, and e-commerce, where web integrity and confidentiality are paramount. The absence of a patch and known exploits means organizations must act proactively to mitigate risk. Failure to address this vulnerability could lead to reputational damage and financial loss, especially given the strict data protection regulations in Europe.

Mitigation Recommendations

European organizations using Piranha CMS should immediately audit their installations to identify if version 12.1 or affected versions are in use. Until an official patch is released, implement strict input validation and sanitization on the Excerpt field to block or neutralize malicious scripts. Employ output encoding techniques to ensure that any user-generated content is safely rendered in browsers. Restrict access to the Page Settings module to trusted administrators only, minimizing the risk of unauthorized content injection. Use Web Application Firewalls (WAFs) with rules designed to detect and block XSS payloads targeting the Excerpt field. Monitor logs for suspicious input patterns or unusual user activity related to content editing. Educate content editors and administrators about the risks of XSS and safe content handling practices. Plan for timely application of patches once available and consider deploying Content Security Policy (CSP) headers to reduce the impact of potential XSS exploits. Regularly review and update security configurations and conduct penetration testing focused on XSS vulnerabilities.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-12-08T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6949a6e09d3de339c6ad0f3b

Added to database: 12/22/2025, 8:15:28 PM

Last enriched: 12/22/2025, 8:30:35 PM

Last updated: 12/23/2025, 7:42:40 AM

Views: 9

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 enhanced features?

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

Latest Threats