{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12512 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12512 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12512 is a medium-severity vulnerability in edge22 GenerateBlocks, published on 13 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-12512 and fix it if it is affected.\n\nWhat it is: CVE-2025-12512 is a medium-severity vulnerability in edge22 GenerateBlocks, published on 13 Dec 2025. 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-12512 in the wild and no public exploit code.\n\nAffected product: edge22 GenerateBlocks. 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-12512/ (Markdown: https://insights.sbomify.com/CVE-2025-12512/index.md)","id":"CVE-2025-12512","markdown":"https://insights.sbomify.com/CVE-2025-12512/index.md","name":"CVE-2025-12512","record":{"aliases":["GHSA-fxjp-p7jh-rpgg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can exfiltrate sensitive user metadata, including PII, due to missing object-level authorization in GenerateBlocks REST API endpoints.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The GenerateBlocks plugin for WordPress is vulnerable to information exposure due to missing object-level authorization checks in versions up to, and including, 2.1.2. This is due to the plugin registering multiple REST API routes under `generateblocks/v1/meta/` that gate access with `current_user_can('edit_posts')`, which is granted to low-privileged roles such as Contributor. The handlers accept arbitrary entity IDs (user IDs, post IDs, etc.) and meta keys, returning any requested metadata with only a short blacklist of password-like keys for protection. There is no object-level authorization ensuring the caller is requesting only their own data, and there is no allowlist of safe keys. This makes it possible for authenticated attackers, with Contributor-level access and above, to exfiltrate personally identifiable information (PII) and other sensitive profile data of administrator accounts or any other users by directly querying user meta keys via the exposed endpoints via the `get_user_meta_rest` function. In typical WordPress + WooCommerce setups, this includes names, email, phone, and address fields that WooCommerce stores in user meta, enabling targeted phishing, account takeover pretexting, and privacy breaches.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"GenerateBlocks \u003c= 2.1.2 - Authenticated (Contributor+) Information Exposure via Metadata","id":"CVE-2025-12512","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"A user with elevated privileges can inject XSS in the Hosts configuration parameters page","id":"CVE-2025-12513"},"packages":[],"prev":{"headline":"A user with elevated privileges can inject XSS in the DSM Administration’s Extensions configuration page","id":"CVE-2025-12511"},"products":["GenerateBlocks"],"published":"2025-12-13","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["edge22"]},"summary":"Authenticated contributors can exfiltrate sensitive user metadata, including PII, due to missing object-level authorization in GenerateBlocks REST API endpoints.","url":"https://insights.sbomify.com/CVE-2025-12512/"}