{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "GenerateBlocks",
          "vendor": "edge22",
          "versions": [
            {
              "lessThanOrEqual": "2.1.2",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "security@wordfence.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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(\u0027edit_posts\u0027)`, 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."
    },
    {
      "lang": "es",
      "value": "El plugin GenerateBlocks para WordPress es vulnerable a la exposici\u00f3n de informaci\u00f3n debido a la falta de comprobaciones de autorizaci\u00f3n a nivel de objeto en versiones hasta, e incluyendo, la 2.1.2. Esto se debe a que el plugin registra m\u00faltiples rutas de la API REST bajo \u0027generateblocks/v1/meta/\u0027 que restringen el acceso con \u0027current_user_can(\u0027edit_posts\u0027)\u0027, lo cual se concede a roles de bajo privilegio como Colaborador. Los manejadores aceptan IDs de entidad arbitrarios (IDs de usuario, IDs de publicaci\u00f3n, etc.) y claves meta, devolviendo cualquier metadato solicitado con solo una corta lista negra de claves similares a contrase\u00f1as para protecci\u00f3n. No hay autorizaci\u00f3n a nivel de objeto que asegure que el llamador est\u00e1 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\u00f3n de identificaci\u00f3n 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\u00e9s de los puntos finales expuestos mediante la funci\u00f3n \u0027get_user_meta_rest\u0027. En configuraciones t\u00edpicas de WordPress + WooCommerce, esto incluye campos de nombre, correo electr\u00f3nico, tel\u00e9fono y direcci\u00f3n que WooCommerce almacena en los metadatos de usuario, lo que permite phishing dirigido, pretexting para toma de control de cuentas y violaciones de privacidad."
    }
  ],
  "id": "CVE-2025-12512",
  "lastModified": "2026-10-07T20:10:01.970",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 4.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 1.4,
        "source": "security@wordfence.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-12512",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-12-15T15:43:58.875682Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-12-13T16:16:46.530",
  "references": [
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/generateblocks/tags/2.1.1/includes/class-meta-handler.php#L297"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/generateblocks/tags/2.1.1/includes/class-meta-handler.php#L56"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/generateblocks/tags/2.1.1/includes/class-meta-handler.php#L61"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/changeset/3415721/generateblocks/trunk/includes/class-meta-handler.php"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/6affdb56-39cc-4749-b7cb-b80b7666f028?source=cve"
    }
  ],
  "sourceIdentifier": "security@wordfence.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-200"
        }
      ],
      "source": "security@wordfence.com",
      "type": "Secondary"
    }
  ]
}