{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-3129 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2011-3129 is a critical vulnerability in Wordpress Wordpress, published on 10 Aug 2011. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-3129 and fix it if it is affected.\n\nWhat it is: CVE-2011-3129 is a critical vulnerability in Wordpress Wordpress, published on 10 Aug 2011. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2011-3129 in the wild and no public exploit code.\n\nAffected product: Wordpress Wordpress. 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-2011-3129/ (Markdown: https://insights.sbomify.com/CVE-2011-3129/index.md)","id":"CVE-2011-3129","markdown":"https://insights.sbomify.com/CVE-2011-3129/index.md","name":"CVE-2011-3129","record":{"aliases":["DEBIAN-CVE-2011-3129","GHSA-v556-6q84-9x6w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress CMS","requires_auth":"low_privilege","summary":"Attacker can upload malicious files with dangerous names in WordPress if server security settings are misconfigured, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wordpress","vendor":"wordpress"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"The file upload functionality in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2, when running \"on hosts with dangerous security settings,\" has unknown impact and attack vectors, possibly related to dangerous filenames.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"File upload in n/a","id":"CVE-2011-3129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wordpress:wordpress","products":["wordpress:wordpress"],"type":"file_upload","year":"2011"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2011-3130"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2011-3128"},"products":["n/a"],"published":"2011-08-10","related":[{"cvss_score":9.8,"headline":"WordPress Core Interpretation Conflict","id":"CVE-2026-63030","kev_date_added":"2026-07-21","published":"2026-07-17"},{"cvss_score":8.1,"headline":"WordPress Core Remote File Inclusion","id":"CVE-2026-87902","kev_date_added":"2026-09-25","published":"2026-09-22"},{"cvss_score":5.9,"headline":"WordPress Core SQL Injection","id":"CVE-2026-60137","kev_date_added":"2026-07-21","published":"2026-07-17"},{"cvss_score":10,"headline":"Cross-site scripting in n/a","id":"CVE-2012-2399","kev_date_added":null,"published":"2012-04-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2012-2400","kev_date_added":null,"published":"2012-04-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3122","kev_date_added":null,"published":"2011-08-10"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-3125","kev_date_added":null,"published":"2011-08-10"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attacker can upload malicious files with dangerous names in WordPress if server security settings are misconfigured, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2011-3129/"}