{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5961 exists.","fix":"No fix has been published for CVE-2013-5961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-5961 is a medium-severity vulnerability in n/a, published on 30 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-5961 and fix it if it is affected.\n\nWhat it is: CVE-2013-5961 is a medium-severity vulnerability in n/a, published on 30 Sep 2013. 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-2013-5961 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-5961/ (Markdown: https://insights.sbomify.com/CVE-2013-5961/index.md)","id":"CVE-2013-5961","markdown":"https://insights.sbomify.com/CVE-2013-5961/index.md","name":"CVE-2013-5961","record":{"aliases":["GHSA-269q-phhx-gq68"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code by uploading a malicious file to the Lazy SEO WordPress plugin.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lazy_seo","vendor":"danny_morris"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Unrestricted file upload vulnerability in lazyseo.php in the Lazy SEO plugin 1.1.9 for WordPress allows remote attackers to execute arbitrary PHP code by uploading a PHP file, then accessing it via a direct request to the file in lazy-seo/.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2013-09-22","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2013-09-22","kind":"exploitdb","ref":"28452","stars":null,"title":"WordPress Plugin Lazy SEO 1.1.9 - Arbitrary File Upload"}],"tier":"weaponised"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2013-5961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2013"},"n_packages":0,"n_references":4,"next":{"headline":"File upload in n/a","id":"CVE-2013-5962"},"packages":[],"prev":{"headline":"Missing Cryptographic Step in OWASP Enterprise Security API for Java","id":"CVE-2013-5960"},"products":["n/a"],"published":"2013-09-30","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":"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 execute arbitrary PHP code by uploading a malicious file to the Lazy SEO WordPress plugin.","url":"https://insights.sbomify.com/CVE-2013-5961/"}