dotnetfoundation vulnerabilities
Recent CVEs affecting dotnetfoundation products. 6 tracked.
dotnetfoundation has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-12-22. Highest priority: CVE-2025-57692 (score 35/100).
- CVE-2025-67291 MEDIUM 6.1 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the Media module of Piranha CMS v12.1 allows attackers to
- CVE-2025-67290 MEDIUM 6.1 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the Page Settings module of Piranha CMS v12.1 allows atta
- CVE-2025-61413 MEDIUM 6.1 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the /manager/pages component of Piranha CMS v12.0 allows
- CVE-2025-57692 MEDIUM 6.8 DOWNGRADE PiranhaCMS 12.0 allows stored XSS in the Text content block of Standard and Standard Archive Pages via /manage
- CVE-2024-55342 MEDIUM 4.7 DOWNGRADE A file upload functionality in Piranha CMS 11.1 allows authenticated remote attackers to upload a crafted PDF
- CVE-2024-55341 MEDIUM 4.7 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in Piranha CMS 11.1 allows remote attackers to execute arbit
FAQ
How do I fix dotnetfoundation vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is dotnetfoundation being exploited right now?
None of the tracked dotnetfoundation CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which dotnetfoundation CVE should I patch first?
CVE-2025-57692 currently ranks highest (35/100): PiranhaCMS 12.0 allows stored XSS in the Text content block of Standard and Standard Archive Pages via /manage.