{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12030 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12030 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12030 is a medium-severity missing authorization vulnerability in airesvsg ACF to REST API, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12030 and fix it if it is affected.\n\nWhat it is: CVE-2025-12030 is a medium-severity missing authorization vulnerability in airesvsg ACF to REST API, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-12030 in the wild and no public exploit code.\n\nAffected product: airesvsg ACF to REST API. 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-2025-12030/ (Markdown: https://insights.sbomify.com/CVE-2025-12030/index.md)","id":"CVE-2025-12030","markdown":"https://insights.sbomify.com/CVE-2025-12030/index.md","name":"CVE-2025-12030","record":{"aliases":["GHSA-g9gc-23hp-3qj2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can modify arbitrary posts, users, and site options due to insufficient permission checks in the ACF to REST API plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The ACF to REST API plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.3.4. This is due to insufficient capability checks in the update_item_permissions_check() method, which only verifies that the current user has the edit_posts capability without checking object-specific permissions (e.g., edit_post($id), edit_user($id), manage_options). This makes it possible for authenticated attackers, with Contributor-level access and above, to modify ACF fields on posts they do not own, any user account, comments, taxonomy terms, and even the global options page via the /wp-json/acf/v3/{type}/{id} endpoints, granted they can authenticate to the site.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-01-06","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-01-06T21:17:57Z","kind":"github_poc","ref":"https://github.com/SnailSploit/CVE-2025-12030","stars":1,"title":"ACF to REST API WordPress Plugin IDOR Vulnerability (CVE-2025-12030) - Security flaw allowing authenticated users with Contributor-level access to modify ACF fields on objects they do not own."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Missing authorization in ACF to REST API","id":"CVE-2025-12030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"HTTP Security Misconfiguration - Lacking Secure and HTTPOnly Attribute","id":"CVE-2025-12031"},"packages":[],"prev":{"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab","id":"CVE-2025-12029"},"products":["ACF to REST API"],"published":"2026-01-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["airesvsg"]},"summary":"Authenticated contributors can modify arbitrary posts, users, and site options due to insufficient permission checks in the ACF to REST API plugin.","url":"https://insights.sbomify.com/CVE-2025-12030/"}