CVE-2025-12512
GenerateBlocks <= 2.1.2 - Authenticated (Contributor+) Information Exposure via Metadata
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.
INFO
Published Date :
Dec. 13, 2025, 4:16 p.m.
Last Modified :
Oct. 7, 2026, 8:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | MEDIUM | MITRE-CVE | ||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update GenerateBlocks plugin to version 2.1.3 or later.
- Verify plugin settings for proper authorization.
- Review user roles and permissions.
- Monitor for unauthorized data access.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-12512.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-12512 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-12512
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-12512 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-12512 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 07, 2026
Action Type Old Value New Value Added Translation Title: GenerateBlocks de edge22, Description: El plugin GenerateBlocks para WordPress es vulnerable a la exposición de información debido a la falta de comprobaciones de autorización a nivel de objeto en versiones hasta, e incluyendo, la 2.1.2. Esto se debe a que el plugin registra múltiples rutas de la API REST bajo 'generateblocks/v1/meta/' que restringen el acceso con 'current_user_can('edit_posts')', lo cual se concede a roles de bajo privilegio como Colaborador. Los manejadores aceptan IDs de entidad arbitrarios (IDs de usuario, IDs de publicación, etc.) y claves meta, devolviendo cualquier metadato solicitado con solo una corta lista negra de claves similares a contraseñas para protección. No hay autorización a nivel de objeto que asegure que el llamador está solicitando solo sus propios datos, y no hay una lista blanca de claves seguras. Esto hace posible que atacantes autenticados, con acceso de nivel Colaborador y superior, exfiltren información de identificación personal (PII) y otros datos de perfil sensibles de cuentas de administrador o de cualquier otro usuario consultando directamente las claves meta de usuario a través de los puntos finales expuestos mediante la función 'get_user_meta_rest'. En configuraciones típicas de WordPress + WooCommerce, esto incluye campos de nombre, correo electrónico, teléfono y dirección que WooCommerce almacena en los metadatos de usuario, lo que permite phishing dirigido, pretexting para toma de control de cuentas y violaciones de privacidad. -
CVE Modified by [email protected]
Jun. 17, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'edge22', 'product': 'GenerateBlocks', 'versions': [{'status': 'affected', 'version': '0', 'versionType': 'semver', 'lessThanOrEqual': '2.1.2'}], 'defaultStatus': 'unaffected'}] -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 17, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2025-12512', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2025-12-15T15:43:58.875682Z'} -
New CVE Received by [email protected]
Dec. 13, 2025
Action Type Old Value New Value Added 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. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Added CWE CWE-200 Added Reference https://plugins.trac.wordpress.org/browser/generateblocks/tags/2.1.1/includes/class-meta-handler.php#L297 Added Reference https://plugins.trac.wordpress.org/browser/generateblocks/tags/2.1.1/includes/class-meta-handler.php#L56 Added Reference https://plugins.trac.wordpress.org/browser/generateblocks/tags/2.1.1/includes/class-meta-handler.php#L61 Added Reference https://plugins.trac.wordpress.org/changeset/3415721/generateblocks/trunk/includes/class-meta-handler.php Added Reference https://www.wordfence.com/threat-intel/vulnerabilities/id/6affdb56-39cc-4749-b7cb-b80b7666f028?source=cve