CVE-2026-32495
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 Link Software LLC WP Terms Popup wp-terms-popup allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Terms Popup: from n/a through <= 2.10.0.
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 confidenceThe WP Terms Popup plugin for WordPress versions through 2.10.0 contains a missing authorization vulnerability (CWE-862) that allows attackers to bypass access control checks and modify popup settings or functionality without proper authentication. This broken access control issue enables unauthorized users to interact with administrative functions intended only for privileged users.
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 WP Terms Popup plugin is installedGo to WordPress admin dashboard > Plugins and locate 'WP Terms Popup' in the installed plugins listAffected if Plugin appears in the plugins list and is activated
-
Determine installed plugin versionClick on the plugin from the Plugins page to view details, or open wp-content/plugins/wp-terms-popup/readme.txt and locate the version line (e.g., 'Stable tag: X.X.X')Affected if Version is 2.10.0 or any version lower than the latest patched release
-
Identify exposed admin AJAX actionsReview plugin PHP files in wp-content/plugins/wp-terms-popup/ for wp_ajax_ hooks (e.g., wp_ajax_wptermspopup_save) and check if they include current_user_can() or similar capability checks before processing requestsAffected if AJAX action handlers lack proper capability verification and are accessible to unauthenticated users
-
Check plugin settings accessibilityAttempt to access the plugin settings page directly via /wp-admin/admin.php?page=wp-terms-popup while logged out as a subscriber-level user, or inspect the plugin code for admin page access controlsAffected if Settings page or related functions are accessible without administrator privileges
If the plugin is active and the installed version is 2.10.0 or lower, the missing authorization vulnerability is present in the environment.
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 to the latest patched version of WP Terms Popup; if unavailable, restrict wp-admin access to administrators only or remove the plugin until a fix 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-2026-32495 — 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-2026-32495 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