Is CVE-2025-12449 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-12449 being exploited in the wild.

How severe is CVE-2025-12449?

Medium severity, with a CVSS score of 5.4, published 7 January 2026.

Which products and versions are affected?

aBlocks – WordPress Gutenberg Blocks up to and including 2.4.0.

Is there a fix for CVE-2025-12449?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-12449 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2025-12449?

Check whether you run aBlocks – WordPress Gutenberg Blocks at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-12449: aBlocks WordPress Gutenberg Blocks privilege escalation in AJAX actions

CVE-2025-12449 · Severity: medium · CVSS 5.4 · Published 2026-01-07

aBlocks is a WordPress plugin providing Gutenberg blocks for page building. The plugin fails to properly verify user permissions on multiple AJAX endpoints, allowing authenticated users with basic subscriber-level access to read sensitive configuration data including API keys for email marketing services, block visibility settings, and maintenance mode configuration. This could expose credentials used by website administrators and enable unauthorized modification of website behavior.

Vendors: aBlocks.

Quick answers

Is CVE-2025-12449 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-12449 being exploited in the wild.
How severe is CVE-2025-12449?: Medium severity, with a CVSS score of 5.4, published 7 January 2026.
Which products and versions are affected?: aBlocks – WordPress Gutenberg Blocks up to and including 2.4.0.
Is there a fix for CVE-2025-12449?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-12449 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2025-12449?: Check whether you run aBlocks – WordPress Gutenberg Blocks at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a missing capability check in multiple AJAX action handlers within the aBlocks plugin (versions up to 2.4.0). Authenticated attackers with subscriber-level access or above can call AJAX endpoints that lack proper permission validation, allowing them to read plugin settings, block visibility rules, maintenance mode configuration, and third-party API keys for email marketing services. The vulnerable code is located in includes/ajax/settings.php and related files. No special network conditions or user interaction is required beyond initial authentication (any authenticated WordPress user). An attacker can retrieve sensitive API credentials and configuration data, potentially leading to account takeover on third-party services or unauthorized modification of website functionality.

Affected products

aBlocks aBlocks – WordPress Gutenberg Blocks up to and including 2.4.0

Timeline

2026-01-07: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.