How severe is CVE-2024-47528?

No CVSS score has been assigned to CVE-2024-47528 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-47528?

CVE-2024-47528 affects the following packages: librenms/librenms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-47528?

Update librenms/librenms to 24.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47528 is resolved across your whole dependency graph.

How do I detect CVE-2024-47528 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for librenms/librenms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-47528 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-47528 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-47528, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-47528?

CVE-2024-47528 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-47528?

CVE-2024-47528 is classified as Cross-site Scripting (XSS) (CWE-79), CWE-116 (CWE-116), Unrestricted File Upload (CWE-434). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-47528 published, and has it been updated?

CVE-2024-47528 was published on October 1, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2024-47528 — librenms

Fix: librenms/librenms@d959bf1

CVE-2024-47528 is a Cross-site Scripting (XSS) vulnerability in librenms/librenms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for librenms/librenms — see the affected versions and patch details below.

LibreNMS Contains a Stored XSS via File Upload

Also known asGHSA-x8gm-j36p-fppf

Published

Oct 1, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47528.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘librenms/librenms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Stored Cross-Site Scripting (XSS) can archive via Uploading a new Background for a Custom Map.

Details

Users with "admin" role can set background for a custom map, this allow the upload of SVG file that can contain XSS payload which will trigger onload. This led to Stored Cross-Site Scripting (XSS).

PoC

Login using an Admin role account.
Go over to "$URL/maps/custom", the Manage Custom Maps.
Create a new map then choose to edit it.
Choose the "Set Background" option.
Choose to upload a SVG file that have this content.

<svg xmlns="http://www.w3.org/2000/svg" onload="alert(document.domain)">
  <circle cx="50" cy="50" r="40" />
</svg>

Once uploaded, there should be a link to the SVG return in the POST request to the API "$URL/maps/custom/1/background".
Go over to that link on browser, should see a pop-up.

Impact

Attacker can use this to perform malicious java script code for malicious intent. This would impact other Admin role users and the Global Read role users. Normal users does not have permission to read the file, so they are not affected.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`librenms/librenms`	all versions	24.9.0`composer require librenms/librenms:^24.9.0`

Affected Products

1 product · 1 configurations

Application

librenmslibrenms

< 24.9.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

LibreNMS is an open-source, PHP/MySQL/SNMP-based network monitoring syst…

github.comNVDDec 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for librenms/librenms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update librenms/librenms to 24.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47528 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Summary Stored Cross-Site Scripting (XSS) can archive via Uploading a new Background for a Custom Map. ### Details Users with "admin" role can set background for a custom map, this allow the upload of SVG file that can contain XSS payload which will trigger onload. This led to Stored Cross-Site Scripting (XSS). ### PoC 1. Login using an Admin role account. 2. Go over to "$URL/maps/custom", the Manage Custom Maps. ![image](https://github.com/user-attachments/assets/9d621532-7880-4010-b12d-efd377f0cfdd) 3. Create a new map then choose to edit it. 4. Choose the "Set Background" option. ![

O3 Security · Impact-Aware SCA

Is CVE-2024-47528 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works