CVE-2025-57692

CVE-2025-57692 is a medium-severity vulnerability in Dotnetfoundation Piranha Cms with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-79.

Key facts

Description

PiranhaCMS 12.0 allows stored XSS in the Text content block of Standard and Standard Archive Pages via /manager/pages, enabling execution of arbitrary JavaScript in another user s browser.

Frequently asked questions

What is CVE-2025-57692?
PiranhaCMS 12.0 allows stored XSS in the Text content block of Standard and Standard Archive Pages via /manager/pages, enabling execution of arbitrary JavaScript in another user s browser.
How severe is CVE-2025-57692?
CVE-2025-57692 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity low, and availability low.
Is CVE-2025-57692 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-57692?
CVE-2025-57692 affects Dotnetfoundation Piranha Cms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-57692?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-57692 have an EU (EUVD) identifier?
Yes. CVE-2025-57692 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31385.
When was CVE-2025-57692 published?
CVE-2025-57692 was published on 2025-09-26 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Dotnetfoundation Piranha Cms

All CVEs affecting Dotnetfoundation Piranha Cms →

Other CWE-79 (Cross-site Scripting (XSS)) vulnerabilities

Browse all CWE-79 (Cross-site Scripting (XSS)) vulnerabilities →