CVE-2026-3454
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe GenerateBlocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2.0. This is due to missing object-level authorization checks in the /wp-json/generateblocks/v1/dynamic-tag-replacements REST endpoint. The endpoint only verifies that the user has the edit_posts capability but does not verify the user has permission to access the specific post or its associated data referenced by attacker-controlled id parameters in dynamic tag content. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive information from arbitrary posts including author email addresses and non-protected post meta values by crafting dynamic tag payloads such as {{post_meta id:<target>|key:<meta_key>}} and {{post_title id:<target>|link:author_email}}.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe GenerateBlocks plugin for WordPress has an Insecure Direct Object Reference (IDOR) vulnerability in the /wp-json/generateblocks/v1/dynamic-tag-replacements REST endpoint. The endpoint only validates that users have edit_posts capability but fails to verify authorization for the specific post referenced by id parameters in dynamic tag content. Authenticated attackers with Contributor-level access can extract sensitive data from arbitrary posts using crafted payloads like {{post_meta id:<target>|key:<meta_key>}} and {{post_title id:<target>|link:author_email}}.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm GenerateBlocks plugin is installedNavigate to WordPress admin > Plugins and locate GenerateBlocks, or check the plugins directory (/wp-content/plugins/) for the generateblocks folder and read the main PHP file's version headerAffected if GenerateBlocks plugin is present in the installation
-
Identify installed GenerateBlocks versionCheck the plugin's main file (usually generateblocks.php) for the Version header in the plugin comment block, or view the plugin details in WordPress admin plugins listAffected if The installed version matches or falls within the affected version range (check against official vulnerability disclosure for exact vulnerable versions)
-
Verify the REST API endpoint is accessibleSend a GET request to /wp-json/generateblocks/v1/dynamic-tag-replacements using a tool like curl or Burp Suite. Include valid WordPress nonces and authentication cookiesAffected if The endpoint returns a 200 OK response rather than 404 or 401
-
Confirm user role has Contributor accessCheck if the testing account has the Contributor role (or any role with edit_posts capability but not full administrative privileges)Affected if The authenticated user has Contributor-level permissions or higher but does NOT have permission to edit the target post
-
Test IDOR by requesting data from an unauthorized postSend a POST request to the dynamic-tag-replacements endpoint with a payload such as {"content":"{{post_meta id:<target_post_id>|key:<sensitive_meta_key>}}"} where <target_post_id> is a post the user cannot normally edit. Include authentication credentialsAffected if The response returns the sensitive post meta data from the unauthorized post, confirming the IDOR vulnerability
A user is affected if they have GenerateBlocks installed with a vulnerable version, the REST endpoint is active, and a Contributor-level user can retrieve data from posts they do not have permission to access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement proper object-level authorization checks in the dynamic-tag-replacements REST endpoint to verify the authenticated user has permission to access the specific post before returning any data.
GenerateBlocks version 2.2.1 or later
- 1. Log in to the WordPress admin dashboard with administrator privileges.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate the GenerateBlocks plugin in the list.
- 4. If an update is available, click 'Update Now' to install the latest version.
- 5. After updating, verify the plugin is running version 2.2.1 or later.
- 6. Test that the dynamic tag functionality still works correctly for authorized users.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3454 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data