{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5099 exists.","fix":"No fix has been published for CVE-2013-5099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-5099 is a low-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2013. 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-2013-5099 and fix it if it is affected.\n\nWhat it is: CVE-2013-5099 is a low-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2013. 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-2013-5099 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-2013-5099/ (Markdown: https://insights.sbomify.com/CVE-2013-5099/index.md)","id":"CVE-2013-5099","markdown":"https://insights.sbomify.com/CVE-2013-5099/index.md","name":"CVE-2013-5099","record":{"aliases":["GHSA-vpjg-mf6g-q65x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Anchor CMS","requires_auth":"none","summary":"Remote attackers can inject arbitrary web script via the Name field in Anchor CMS when comments are enabled, requiring user interaction to execute.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anchor_cms","vendor":"anchor"}],"cvss":{"score":2.6,"severity":"low","source":"nvd","vector":"AV:N/AC:H/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Cross-site scripting (XSS) vulnerability in article.php in Anchor CMS 0.9.1, when comments are enabled, allows remote attackers to inject arbitrary web script or HTML via the Name field.  NOTE: some sources have reported that comments.php is vulnerable, but certain functions from comments.php are used by article.php.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2013-07-18","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2013-07-18","kind":"exploitdb","ref":"26958","stars":null,"title":"Anchor CMS 0.9.1 - Persistent Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2013-5099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Static Methods since 2007 (div2007) extension for TYPO3 vulnerable to Cross-site Scripting","id":"CVE-2013-5100"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-5098"},"products":["n/a"],"published":"2013-08-09","related":[],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script via the Name field in Anchor CMS when comments are enabled, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2013-5099/"}