CVE-2025-26944
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 · uneditedMissing Authorization vulnerability in Crocoblock JetPopup jet-popup allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects JetPopup: from n/a through <= 2.0.11.
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 · moderate confidenceMissing authorization vulnerability in Crocoblock JetPopup plugin allows unauthenticated or unauthorized users to access functionality that should be constrained by access control lists (ACLs). The issue affects versions up to and including 2.0.11, potentially enabling attackers to manipulate popup behaviors or access administrative functionality without proper authentication.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 JetPopup plugin is installedNavigate to WordPress admin dashboard > Plugins and verify JetPopup (by Crocoblock) appears in the installed plugins listAffected if JetPopup plugin is present and active in the WordPress installation
-
Check installed JetPopup versionIn Plugins list, locate JetPopup and view the version number displayed below the plugin name; or check the plugin header in /wp-content/plugins/jetpopup/jetpopup.phpAffected if The installed version is 2.0.11 or any earlier version (the vulnerability affects versions up to and including 2.0.11)
-
Identify exposed AJAX endpointsSearch plugin files for wp_ajax and wp_ajax_nopriv hooks in jetpopup.php or related files within the /jetpopup/includes/ directoryAffected if Any JetPopup AJAX endpoints are registered with wp_ajax_nopriv hooks (allowing unauthenticated access)
-
Review access to popup administrative functionsTest accessing JetPopup popup editor or settings pages directly via URL without being logged in as an administratorAffected if Unauthenticated or low-privilege users can access popup creation, editing, or settings pages that should require admin privileges
-
Inspect server logs for suspicious JetPopup requestsExamine access logs for POST requests to /wp-admin/admin-ajax.php with JetPopup-related actions (jetpopup_*) from unknown or anonymous IP addressesAffected if Logs show requests to JetPopup AJAX actions originating from unauthenticated sources
Your environment is affected if the JetPopup plugin is installed with version 2.0.11 or lower and AJAX endpoints or administrative functions are accessible without proper 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 JetPopup to a version beyond 2.0.11 that implements proper authorization checks, or disable the plugin until a patched version is available. If immediate patching is not possible, review and restrict access to JetPopup-related AJAX endpoints at the server level.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26944 — 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-26944 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