CVE-2025-11370
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 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.
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 Depicter WordPress plugin versions up to 4.0.7 lack a capability check on the 'store' function in the RulesAjaxController class, allowing unauthenticated attackers to modify popup display settings via the AJAX endpoint. This is a broken access control vulnerability where the endpoint accepts requests from any user without verifying authorization.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Depicter plugin is installedCheck the WordPress plugins directory for the Depicter plugin folder, or query the wp_posts table for post_type='plugin' and post_title containing 'Depicter'Affected if The Depicter plugin files exist in the WordPress installation
-
Check installed Depicter versionOpen the main plugin file (depicter.php) in the /wp-content/plugins/depicter/ directory and read the Version header from the plugin comment block, or check the wp_options table for the option_name containing 'depicter_version'Affected if The version number is 4.0.7 or lower
-
Identify the vulnerable AJAX endpointLocate the RulesAjaxController class file within the plugin directory (typically in a classes or controllers subfolder), and identify the AJAX action hook that registers the 'store' function - this is the vulnerable endpointAffected if The RulesAjaxController class with a 'store' method exists and is registered as a WordPress AJAX action (wp_ajax_ or wp_ajax_nopriv_) without capability checks
-
Confirm endpoint lacks authenticationReview the code in the RulesAjaxController class 'store' function for any current_user_can() or capability verification calls; also check the AJAX action registration to see if it uses wp_ajax_nopriv_ (allowing unauthenticated access)Affected if The store function has no current_user_can() check and the AJAX action is registered with wp_ajax_nopriv_ or lacks any auth requirement
A user is affected if they have Depicter plugin version 4.0.7 or lower installed with the RulesAjaxController AJAX endpoint accessible without authentication.
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 dataUpgrade to version 4.0.8 or later which adds proper capability checks. If immediate patching is not possible, consider restricting access to the affected AJAX endpoint via .htaccess or firewall rules.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11370 — 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-2025-11370 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