CVE-2026-2295
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 WPZOOM Addons for Elementor – Starter Templates & Widgets plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'ajax_post_grid_load_more' function in all versions up to, and including, 1.3.2. This makes it possible for unauthenticated attackers to retrieve protected (draft, future, pending) post titles and excerpts that should not be accessible to unauthenticated users.
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 WPZOOM Addons for Elementor plugin has a broken access control vulnerability in the 'ajax_post_grid_load_more' function lacking capability checks, allowing unauthenticated attackers to query and retrieve protected posts (draft, future, pending) including their titles and excerpts that should not be publicly accessible.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Verify WPZOOM Addons for Elementor is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WPZOOM Addons for Elementor' or check the plugin files in /wp-content/plugins/Affected if Plugin is not installed - not affected. If installed, continue to version check.
-
Check installed plugin versionIn WordPress admin > Plugins, find WPZOOM Addons for Elementor and note the version number displayed, or read version from plugin main file headerAffected if Version is unknown, lower than, or not confirmed to be 1.3.3 or later - potentially affected
-
Confirm the vulnerable function existsCheck plugin source code for the 'ajax_post_grid_load_more' function in the plugin files - look for a PHP function with this exact nameAffected if Function exists in the codebase and the plugin version is below 1.3.3 - vulnerable function is present
-
Test unauthenticated access to protected postsSend a crafted AJAX request to wp-admin/admin-ajax.php with action=post_grid_load_more or similar, without authenticating, to see if draft/future/pending posts are returned in the responseAffected if Unauthenticated requests return titles/excerpts of non-public (draft, future, pending) posts - vulnerability is present and exploitable
User is affected if WPZOOM Addons for Elementor is installed with a version lower than 1.3.3 AND the ajax_post_grid_load_more function is accessible to unauthenticated users, allowing retrieval of protected post content.
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.
From vendor dataUpdate the plugin to version 1.3.3 or later which includes proper capability checks; alternatively, add WordPress capability verification (e.g., current_user_can('edit_posts')) to the ajax_post_grid_load_more function and restrict access to authenticated users only.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2295 — 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-2295 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