{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-3384 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2012-3384 is a medium-severity vulnerability in Wordpress Wordpress, published on 22 Jul 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2012-3384 and fix it if it is affected.\n\nWhat it is: CVE-2012-3384 is a medium-severity vulnerability in Wordpress Wordpress, published on 22 Jul 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2012-3384 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-2012-3384/ (Markdown: https://insights.sbomify.com/CVE-2012-3384/index.md)","id":"CVE-2012-3384","markdown":"https://insights.sbomify.com/CVE-2012-3384/index.md","name":"CVE-2012-3384","record":{"aliases":["DEBIAN-CVE-2012-3384","GHSA-m93w-3www-hrw9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress CMS","requires_auth":"low_privilege","summary":"Remote attackers can hijack user authentication in WordPress via CSRF in the customizer, requiring victim interaction.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"wordpress","vendor":"wordpress"}],"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":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-site request forgery (CSRF) vulnerability in the customizer in WordPress before 3.4.1 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.","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":"Cross-site request forgery in n/a","id":"CVE-2012-3384","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wordpress:wordpress","products":["wordpress:wordpress"],"type":"csrf","year":"2012"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2012-3385"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2012-3383"},"products":["n/a"],"published":"2012-07-22","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":"Remote attackers can hijack user authentication in WordPress via CSRF in the customizer, requiring victim interaction.","url":"https://insights.sbomify.com/CVE-2012-3384/"}