{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55573 exists.","fix":"No fix has been published for CVE-2025-55573 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55573 is a high-severity cross-site scripting vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55573 and fix it if it is affected.\n\nWhat it is: CVE-2025-55573 is a high-severity cross-site scripting vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, 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-2025-55573 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-55573/ (Markdown: https://insights.sbomify.com/CVE-2025-55573/index.md)","id":"CVE-2025-55573","markdown":"https://insights.sbomify.com/CVE-2025-55573/index.md","name":"CVE-2025-55573","record":{"aliases":["GHSA-8mvm-xhp4-8qjp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"new-api","requires_auth":"none","summary":"Cross-site scripting vulnerability in new-api allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"new_api","vendor":"newapi"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"QuantumNous new-api v.0.8.5.2 is vulnerable to Cross Site Scripting (XSS).","ecosystems":[],"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-2025-55573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-55574"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-55564"},"products":["n/a"],"published":"2025-08-22","related":[{"cvss_score":7.7,"headline":"New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs","id":"CVE-2026-33655","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":7.6,"headline":"New API has Potential XSS in its MarkdownRenderer component","id":"CVE-2026-25802","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":7.1,"headline":"New API: Stripe Webhook Signature Bypass via Empty Secret Enables Unlimited Quota Fraud","id":"CVE-2026-41432","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":7.1,"headline":"New API: SSRF Filter Bypass via 0.0.0.0","id":"CVE-2026-42339","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":7.1,"headline":"New API has an SQL LIKE Wildcard Injection DoS via Token Search","id":"CVE-2026-25591","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":6.5,"headline":"New API: IDOR in VideoProxy allows cross-user video content access via missing ownership check","id":"CVE-2026-30886","kev_date_added":null,"published":"2026-03-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2025-08-22","vendors":["n/a"]},"summary":"Cross-site scripting vulnerability in new-api allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2025-55573/"}