Information Disclosure in GenerateBlocks (WordPress plugin) (CVE-2025-12512)
Summary
Vulnerability in GenerateBlocks (WordPress plugin) (CVE-2025-12512). Risk of unauthorized operations or information disclosure. Exploitable via get_user_meta_rest.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-12512 has been found in GenerateBlocks (WordPress plugin).
Attackers can target a specific entry point like get_user_meta_rest over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GenerateBlocks (WordPress plugin) CVE-2025-12512" on the vendor's site.
CVE-2025-12512 (GenerateBlocks (WordPress plugin)) — CWE-200 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: get_user_meta_rest
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in GenerateBlocks (WordPress plugin). Attackers reach the vulnerable code path via get_user_meta_rest.
Check the vendor advisory for the affected versions of GenerateBlocks (WordPress plugin). Attack surface: get_user_meta_rest.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで GenerateBlocks (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。