CVE-2025-14895
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 PopupKit plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.2.0. This is due to the plugin not properly verifying that a user is authorized to access the /popup/logs REST API endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read and delete analytics data including device types, browser information, countries, referrer URLs, and campaign metrics.
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 PopupKit WordPress plugin fails to perform proper capability checks on its /popup/logs REST API endpoint, allowing any authenticated user with Subscriber-level permissions or higher to access sensitive analytics data including device types, browser information, countries, referrer URLs, and campaign metrics. Attackers can both read and delete this data due to missing authorization verification.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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.
-
Confirm PopupKit plugin is installedCheck the WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin dashboard to verify PopupKit is presentAffected if PopupKit plugin is installed and active
-
Identify the installed PopupKit versionIn WordPress admin, go to Plugins > Installed Plugins and find the PopupKit plugin to view its version numberAffected if The installed version is any version prior to the patched release containing proper REST API capability checks
-
Verify the /popup/logs REST API endpoint is exposedSend an authenticated HTTP request as a low-privilege user (Subscriber role) to /wp-json/popup/v1/logs or /wp-json/popupkit/v1/logsAffected if The endpoint returns analytics data (device types, browser info, countries, referrer URLs, or campaign metrics) without returning a 401 or 403 error
-
Confirm lack of capability enforcement on the endpointUse a tool like WP-CLI to test endpoint access or inspect the plugin's REST API route registration code in the includes directory for capability requirementsAffected if The REST API handler does not include a capability check such as 'manage_options' or a custom capability before returning sensitive data
A user is affected if PopupKit is installed and the /popup/logs REST API endpoint returns sensitive analytics data to any authenticated user with Subscriber-level access without authorization verification.
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 PopupKit to the latest version which implements proper REST API capability checks. If no update is available, manually add current_user_capability checks to the /popup/logs endpoint handlers or disable the endpoint until a patch is released.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14895 — 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-14895 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