CVE-2025-12512
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk27th percentile - higher than 27% of all known CVEs
Summary
The GenerateBlocks plugin for WordPress in versions up to and including 2.1.2 is vulnerable to information exposure due to missing object-level authorization checks. It registers 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 no allowlist of safe keys. This allows 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.
Risk Assessment
A low-privileged attacker (Contributor) can exfiltrate PII and sensitive profile data of administrators and other users. This can lead to targeted phishing, account takeover pretexting, and privacy breaches.
Recommendation
Update the GenerateBlocks plugin to a version newer than 2.1.2 as soon as it becomes available. Until then, limit Contributor roles and monitor for unusual requests to the generateblocks/v1/meta/ REST API routes.
Related vulnerabilities
- CVE-2026-7826Critical
A vulnerability in FalkorDB before 4.18.4 causes a heap-based out-of-bounds read in the BufferSerializerIOv2_ReadBuffer function. A remote attacker who can issue Redis replication commands (e.g., against an instance with no password) can send a crafted RDB stream with a sub-buffer length field exceeding the remaining buffer size. The only bounds check is an ASSERT(), which is compiled out in release builds, so memcpy() reads past the end of the heap allocation.
- CVE-2026-5759Critical
A double free and use-after-free vulnerability in the RdbLoadDeletedNodes function of the RDB graph decoders in FalkorDB before 4.18.1. A remote attacker who can issue Redis replication commands can send a crafted RDB stream where the deleted-nodes buffer length is not a multiple of sizeof(NodeID). The length check relies on ASSERT(), which is compiled out in release builds, so the function continues after freeing the buffer, reading it and freeing it a second time.
- CVE-2026-96207Critical
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
- CVE-2026-94510Critical
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.
- CVE-2026-88131Critical
Deserialization of untrusted data in Microsoft Dataverse allows an unauthorized attacker to execute code over a network.
- CVE-2026-77900Critical
Missing authentication for a critical function in Azure App Service allows an unauthorized attacker to execute code over a network.
- CVE-2026-69435Critical
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.
- CVE-2026-84249Critical
IBM Guardium Data Protection 12.2 and 12.2.2 could allow a remote attacker to execute arbitrary management operations due to missing authentication for a critical function.
- CVE-2026-80381Critical
IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute unauthorized SQL statements due to SQL injection.
- CVE-2026-75875Critical
IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute arbitrary code due to path traversal.
Original NVD description (English 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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS