Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2295: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in wpzoom WPZOOM Addons for Elementor – Starter Templates & Widgets

0
Medium
VulnerabilityCVE-2026-2295cvecve-2026-2295cwe-200
Published: Wed Feb 11 2026 (02/11/2026, 09:27:15 UTC)
Source: CVE Database V5
Vendor/Project: wpzoom
Product: WPZOOM Addons for Elementor – Starter Templates & Widgets

Description

The 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.

AI-Powered Analysis

AILast updated: 02/11/2026, 10:00:38 UTC

Technical Analysis

CVE-2026-2295 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) found in the WPZOOM Addons for Elementor – Starter Templates & Widgets plugin for WordPress. The root cause is a missing capability check in the 'ajax_post_grid_load_more' AJAX handler function, which is responsible for loading additional posts in a grid layout. This flaw allows unauthenticated attackers to invoke this function and retrieve titles and excerpts of posts that are in draft, future, or pending states—content that is normally restricted to authorized users. The vulnerability affects all versions up to and including 1.3.2. The CVSS v3.1 base score is 5.3 (medium severity), reflecting that the attack vector is network-based, requires no privileges or user interaction, and impacts confidentiality only, without affecting integrity or availability. No patches or official fixes are currently listed, and no known exploits have been reported in the wild. The exposure of unpublished content can aid attackers in gathering intelligence about upcoming content, editorial plans, or sensitive information not intended for public disclosure. This can facilitate targeted phishing, social engineering, or more sophisticated attacks against the affected organization’s web infrastructure. The vulnerability is specific to WordPress sites using this plugin, which is popular among users of the Elementor page builder, particularly for creating starter templates and widgets.

Potential Impact

For European organizations, the primary impact is the unauthorized disclosure of sensitive or unpublished content, which can undermine editorial confidentiality and potentially expose business plans or sensitive information. This can damage reputation, lead to competitive disadvantage, or facilitate further attacks such as spear phishing. Although the vulnerability does not allow modification or deletion of content, the leakage of draft or pending posts can be critical for media companies, marketing agencies, or any organization relying on WordPress for content management. The impact is heightened for organizations that use this plugin extensively or rely on unpublished content for strategic communications. Additionally, regulatory implications under GDPR may arise if the leaked content includes personal data or information that should be protected under privacy laws. The lack of known exploits reduces immediate risk, but the ease of exploitation and network accessibility mean attackers could quickly develop exploits if motivated.

Mitigation Recommendations

Organizations should immediately audit their WordPress installations to identify the presence of the WPZOOM Addons for Elementor – Starter Templates & Widgets plugin and verify the version in use. Since no official patch is currently available, temporary mitigations include disabling or removing the plugin until a fix is released. Alternatively, restricting access to the AJAX endpoint 'ajax_post_grid_load_more' via web application firewall (WAF) rules or server-level access controls can prevent unauthenticated requests. Implementing strict capability checks or custom code to validate user permissions before processing AJAX requests is recommended for organizations with development resources. Monitoring web server logs for suspicious access patterns targeting this AJAX function can help detect exploitation attempts. Organizations should also maintain regular backups and ensure their WordPress core and plugins are updated promptly once a patch is released. Finally, reviewing content management workflows to minimize sensitive information exposure in draft or pending posts can reduce risk.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-02-10T16:22:48.874Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698c4ff54b57a58fa188e032

Added to database: 2/11/2026, 9:46:29 AM

Last enriched: 2/11/2026, 10:00:38 AM

Last updated: 2/11/2026, 12:11:13 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats