dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32417

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in wppochipp Pochipp pochipp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Pochipp: from n/a through < 1.18.9.

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 confidence

This is a missing authorization vulnerability in the Pochipp WordPress plugin (wppochipp) affecting versions before 1.18.9. The vulnerability allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to certain plugin functions or data that should require proper authentication.

MitigationUpdate Pochipp plugin to version 1.18.9 or later to receive the authorization fix. Review user roles and permissions settings after updating.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Pochipp plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Pochipp' or 'wppochipp' in the list of active plugins.
    Affected if Pochipp plugin is present and active in the WordPress installation
  2. Identify installed Pochipp version
    In the plugins list, find the Pochipp entry and note the version number displayed below the plugin name. Alternatively, check the plugin header in wp-content/plugins/wppochipp/wppochipp.php for the 'Version' comment tag.
    Affected if Installed version is lower than 1.18.9 (for example, 1.18.8, 1.18.7, etc.)
  3. Inspect plugin access control settings
    Go to Pochipp settings page in WordPress admin (usually under Settings > Pochipp or a dedicated Pochipp menu item). Look for any permission, role, or authorization-related configuration options that control who can access plugin functions.
    Affected if Settings allow low-privileged users (such as subscribers or guests) to access functions that should require admin-level permissions
  4. Test for exposed sensitive endpoints
    Use a browser or HTTP tool to check if Pochipp AJAX endpoints (typically at /wp-admin/admin-ajax.php?action=pochipp_*) or custom plugin endpoints are accessible without proper WordPress authentication or capability checks.
    Affected if Plugin endpoints respond to unauthenticated requests or requests from low-privileged users without proper capability verification

User is affected if the Pochipp plugin is installed with a version before 1.18.9 AND the plugin settings or exposed endpoints permit unauthorized access due to missing authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Pochipp plugin to version 1.18.9 or later to receive the authorization fix. Review user roles and permissions settings after updating.

Recommended fix Moderate confidence

1.18.9

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Pochipp plugin
  4. Click 'Update Now' to update to the latest version (1.18.9 or later)
  5. Alternatively, use WP-CLI: wp plugin update pochipp
  6. Alternatively, manually download the updated plugin from WordPress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects 1.18.9 or higher
  8. Test that the plugin functionality works as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32417 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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