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-2025-11370: CWE-862 Missing Authorization in averta Depicter — Popup & Slider Builder

0
Medium
VulnerabilityCVE-2025-11370cvecve-2025-11370cwe-862
Published: Tue Jan 06 2026 (01/06/2026, 03:21:40 UTC)
Source: CVE Database V5
Vendor/Project: averta
Product: Depicter — Popup & Slider Builder

Description

The Popup and Slider Builder by Depicter – Add Email collecting Popup, Popup Modal, Coupon Popup, Image Slider, Carousel Slider, Post Slider Carousel plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'store' function of the RulesAjaxController class in all versions up to, and including, 4.0.7. This makes it possible for unauthenticated attackers to update pop-up display settings.

AI-Powered Analysis

AILast updated: 01/06/2026, 03:54:52 UTC

Technical Analysis

CVE-2025-11370 identifies a missing authorization vulnerability (CWE-862) in the averta Depicter — Popup & Slider Builder plugin for WordPress, specifically in the 'store' function of the RulesAjaxController class. This function lacks proper capability checks, allowing unauthenticated attackers to update pop-up display settings remotely without requiring any user interaction or authentication. The plugin is widely used to create email collection popups, coupon modals, image sliders, and carousels on WordPress sites. By exploiting this flaw, attackers can manipulate the content and behavior of pop-ups, potentially injecting malicious or misleading information to deceive users, facilitate phishing, or disrupt marketing campaigns. The vulnerability affects all versions up to and including 4.0.7, with no patch currently available as per the provided data. The CVSS v3.1 base score is 5.3, indicating medium severity, with attack vector network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), no confidentiality impact (C:N), limited integrity impact (I:L), and no availability impact (A:N). No known exploits have been reported in the wild, but the ease of exploitation and the potential for misuse in social engineering attacks make it a relevant threat for WordPress site administrators.

Potential Impact

For European organizations, this vulnerability primarily threatens the integrity of web content delivered via pop-ups on WordPress sites using the affected plugin. Unauthorized modification of pop-up settings can lead to the injection of fraudulent messages, phishing attempts, or misleading promotional content, potentially damaging brand reputation and user trust. While it does not directly compromise sensitive data confidentiality or system availability, the indirect consequences include increased risk of credential theft, malware distribution, or customer deception. Organizations relying heavily on pop-up-based marketing, user engagement, or email collection are particularly vulnerable. Given the widespread use of WordPress across Europe, especially in e-commerce, media, and marketing sectors, the vulnerability could be exploited to target customers or employees. The lack of required authentication and user interaction lowers the barrier for attackers, increasing the likelihood of exploitation if unpatched. However, the absence of known active exploits suggests limited immediate impact but warrants proactive mitigation.

Mitigation Recommendations

1. Monitor for official patches or updates from averta and apply them immediately once available to ensure the vulnerability is remediated. 2. Until a patch is released, implement web application firewall (WAF) rules to restrict access to the vulnerable AJAX endpoint, specifically the 'store' function of RulesAjaxController, allowing only authenticated and authorized users. 3. Review and harden WordPress user roles and permissions to minimize exposure of administrative functions. 4. Employ security plugins that can detect and block unauthorized changes to plugin settings or suspicious AJAX requests. 5. Conduct regular audits of pop-up content and configurations to detect unauthorized modifications promptly. 6. Educate site administrators and content managers about this vulnerability and encourage vigilance for unusual pop-up behavior. 7. Consider temporarily disabling the Depicter plugin if the risk outweighs its benefits until a secure version is available. 8. Use network segmentation and monitoring to detect anomalous traffic patterns targeting WordPress AJAX endpoints.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-06T14:00:15.658Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695c838f3839e44175cef8d5

Added to database: 1/6/2026, 3:37:51 AM

Last enriched: 1/6/2026, 3:54:52 AM

Last updated: 1/8/2026, 9:00:02 AM

Views: 18

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