Live › vulnerability › CVE-2025-12544
The Publisher portal does not validate uploaded SVG files, so a user with the Publisher role can upload a crafted SVG that is stored and rendered. When a victim views it, the script can redirect their browser, alter the page, or read information from the browser, though httpOnly session cookies limit session hijacking.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 11:22 UTC. All times on this page are UTC.
The sources do not name the product or version, so exposure is unknown. The flaw needs a Publisher-role account to upload the file, and a victim must then view the stored SVG in a browser. Teams that run a Publisher portal with SVG uploads should look at it.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Publisher portal fails to enforce proper validation on uploaded SVG files, allowing users with the Publisher role to inject malicious scripts. This weakness can be exploited by uploading a crafted SVG file, which is then stored and rendered by the application.
The security consequences include the ability for a malicious actor to redirect the victim's browser to an arbitrary website, modify the web page's UI, or retrieve information from the browser. However, the impact is mitigated as session-related sensitive cookies are protected with the httpOnly flag, preventing session hijacking.
This page as .md · .json · in your agent: get_signal("CVE-2025-12544")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.