{"answers":{"affected":"1 open source package ship an affected version, including pynetbox. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47226 exists.","fix":"No fix has been published for CVE-2024-47226 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47226 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-47226 and fix it if it is affected.\n\nWhat it is: CVE-2024-47226 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47226 exists.\n\nAffected packages and fixed versions:\n- pynetbox (PyPI): affected all versions up to 4.1.0-NA; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-47226/ (Markdown: https://insights.sbomify.com/CVE-2024-47226/index.md)","id":"CVE-2024-47226","markdown":"https://insights.sbomify.com/CVE-2024-47226/index.md","name":"CVE-2024-47226","record":{"aliases":["GHSA-725j-ffcc-fc53","PYSEC-2024-325"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NetBox IPAM","requires_auth":"low_privilege","summary":"Authenticated users can inject JavaScript into the Top banner field, though this is disputed as intended behavior for displaying HTML notifications.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"netbox","vendor":"netbox"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A stored cross-site scripting (XSS) vulnerability exists in NetBox 4.1.0 within the \"Configuration History\" feature of the \"Admin\" panel via a /core/config-revisions/ Add action. An authenticated user can inject arbitrary JavaScript or HTML into the \"Top banner\" field. NOTE: Multiple third parties have disputed this as not a vulnerability. It is argued that the configuration revision banner feature is meant to contain unsanitized HTML in order to display notifications to users. Since these fields are intended to display unsanitized HTML, this is working as intended.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2024-47226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2024"},"n_packages":1,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-47227"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["4.1.0-NA"],"package":"pynetbox","purl":"pkg:pypi/pynetbox","source":"PYSEC-2024-325"}],"prev":{"headline":"Other in n/a","id":"CVE-2024-47224"},"products":["n/a"],"published":"2024-09-22","related":[{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2023-33796","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56917","kev_date_added":null,"published":"2025-06-24"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-40728","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-40729","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-40732","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-40738","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-40740","kev_date_added":null,"published":"2024-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-11","vendors":["n/a"]},"summary":"Authenticated users can inject JavaScript into the Top banner field, though this is disputed as intended behavior for displaying HTML notifications.","url":"https://insights.sbomify.com/CVE-2024-47226/"}