{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1001000 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2017-1001000 is a high-severity missing authorization vulnerability in Wordpress Wordpress, published on 3 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1001000 and fix it if it is affected.\n\nWhat it is: CVE-2017-1001000 is a high-severity missing authorization vulnerability in Wordpress Wordpress, published on 3 Apr 2017. 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-2017-1001000 exists.\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-2017-1001000/ (Markdown: https://insights.sbomify.com/CVE-2017-1001000/index.md)","id":"CVE-2017-1001000","markdown":"https://insights.sbomify.com/CVE-2017-1001000/index.md","name":"CVE-2017-1001000","record":{"aliases":["DEBIAN-CVE-2017-1001000","GHSA-qm68-r9p4-ghhx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress REST API","requires_auth":"none","summary":"Remote attackers can modify arbitrary pages by exploiting improper input validation in the WordPress REST API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"joshbressers","cpe":[{"product":"wordpress","vendor":"wordpress"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers to modify arbitrary pages via a request for wp-json/wp/v2/posts followed by a numeric value and a non-numeric value, as demonstrated by the wp-json/wp/v2/posts/123?id=123helloworld URI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2017-02-01","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2017-02-01","kind":"metasploit","ref":"auxiliary/scanner/http/wordpress_content_injection","stars":null,"title":"WordPress REST API Content Injection"}],"tier":"weaponised"},"has_fix":true,"headline":"Missing authorization in n/a","id":"CVE-2017-1001000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wordpress:wordpress","products":["wordpress:wordpress"],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":9,"next":{"headline":"Cross-site scripting in PluXml","id":"CVE-2017-1001001"},"packages":[],"prev":{"headline":"WordPress version \u003c4.9 contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution.","id":"CVE-2017-1000600"},"products":["n/a"],"published":"2017-04-03","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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can modify arbitrary pages by exploiting improper input validation in the WordPress REST API endpoints.","url":"https://insights.sbomify.com/CVE-2017-1001000/"}