{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50579 exists.","fix":"No fix has been published for CVE-2025-50579 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50579 is a medium-severity vulnerability in n/a, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-50579 and fix it if it is affected.\n\nWhat it is: CVE-2025-50579 is a medium-severity vulnerability in n/a, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50579 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-50579/ (Markdown: https://insights.sbomify.com/CVE-2025-50579/index.md)","id":"CVE-2025-50579","markdown":"https://insights.sbomify.com/CVE-2025-50579/index.md","name":"CVE-2025-50579","record":{"aliases":["GHSA-h493-5cp7-m669"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Nginx Proxy Manager","requires_auth":"none","summary":"Attackers can steal JWT tokens via CORS misconfiguration in Nginx Proxy Manager, enabling unauthorized access and data exfiltration.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nginx_proxy_manager","vendor":"jc21"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1259","name":"Improper Restriction of Security Token Assignment"}],"description":"A CORS misconfiguration in Nginx Proxy Manager v2.12.3 allows unauthorized domains to access sensitive data, particularly JWT tokens, due to improper validation of the Origin header. This misconfiguration enables attackers to intercept tokens using a simple browser script and exfiltrate them to a remote attacker-controlled server, potentially leading to unauthorized actions within the application.","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":"Misconfiguration in n/a","id":"CVE-2025-50579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-50581"},"packages":[],"prev":{"headline":"Open redirect in n/a","id":"CVE-2025-50578"},"products":["n/a"],"published":"2025-08-19","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-46256","kev_date_added":null,"published":"2024-09-27"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-27224","kev_date_added":null,"published":"2023-03-22"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2024-39935","kev_date_added":null,"published":"2024-07-04"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-23596","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":6.3,"headline":"Command injection in n/a","id":"CVE-2024-46257","kev_date_added":null,"published":"2024-09-27"},{"cvss_score":5.5,"headline":"Path traversal in n/a","id":"CVE-2019-15517","kev_date_added":null,"published":"2019-08-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":"partial"},"state":"PUBLISHED","updated":"2025-08-19","vendors":["n/a"]},"summary":"Attackers can steal JWT tokens via CORS misconfiguration in Nginx Proxy Manager, enabling unauthorized access and data exfiltration.","url":"https://insights.sbomify.com/CVE-2025-50579/"}