CVE-2025-67291: A stored cross-site scripting (XSS) vulnerability in the Media module of Piranha CMS v12.1 allows attackers...
A stored cross-site scripting (XSS) vulnerability in the Media module of Piranha CMS v12.1 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Name field.
Security readout for executives and security teams
Plain-English summary
Piranha CMS v12.1 has a stored XSS issue in the Media module. A crafted media Name can persist and later run script or HTML in another user’s browser. This creates business risk around admin session misuse, content tampering, or limited data exposure, but the provided CVSS indicates user interaction is required.
Executive priority
Treat this as a moderate web application risk. Prioritize confirmation for internet-facing CMS administration or multi-user content workflows, then apply vendor guidance when available and reduce who can write media metadata.
Technical view
CVE-2025-67291 is CWE-79 stored cross-site scripting in the Media module Name field. The CVSS 3.1 score is 6.1 with network attack vector, low complexity, no privileges required, user interaction required, changed scope, low confidentiality impact, low integrity impact, and no availability impact.
Likely exposure
Most relevant to environments running Piranha CMS v12.1 where the Media module is enabled and users can create or edit media names. The source bundle’s affected-product metadata is incomplete, so exposure should be confirmed through software inventory rather than CPE matching.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. The cited GitHub reference indicates a reported stored XSS condition, but exploitation status beyond public disclosure is not evidenced in the provided sources.
Researcher notes
The record names Piranha CMS v12.1 and the Media module Name field, but structured affected-vendor/product data is marked n/a. Avoid broad version assumptions. Evidence supports stored XSS characteristics, not confirmed exploitation or a named patch.
Mitigation direction
Check Piranha CMS vendor or project guidance for an official fix or advisory.
Restrict Media module write access to trusted authenticated users only.
Review application-side output encoding for media Name rendering paths.
Sanitize existing media Name values containing script or HTML-like content.
Increase monitoring for suspicious changes to media metadata.
Validation and detection
Inventory Piranha CMS deployments and identify any v12.1 instances.
Confirm whether the Media module is enabled and who can edit Name fields.
Review stored media Name values for unexpected script or HTML content.
Check whether rendered media names are safely encoded in admin and public views.
Track the CVE record and project reference for updated remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.