dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32425

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 linknacional Payment Gateway Pix For GiveWP payment-gateway-pix-for-givewp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Payment Gateway Pix For GiveWP: from n/a through <= 2.2.3.

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

Missing authorization vulnerability in Payment Gateway Pix For GiveWP plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to sensitive payment-related functionality, potentially enabling unauthorized configuration changes or payment operations.

MitigationUpdate Payment Gateway Pix For GiveWP to the latest version beyond 2.2.3 to obtain the authorization fix. Review all plugin endpoints and ensure proper capability checks are enforced on administrative and payment processing functions.

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 checks

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

  1. Verify Payment Gateway Pix For GiveWP plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Payment Gateway Pix For GiveWP' or search for it. Alternatively, check the wp-content/plugins directory for a folder containing 'pix' and 'givewp' in the name.
    Affected if The plugin appears in the list of installed plugins and is activated
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Click on the plugin name or view the plugin file header (usually in the main PHP file) to find the version number. You can also check via FTP or file manager in wp-content/plugins/[plugin-folder]/readme.txt or the main plugin PHP file for the 'Version' header.
    Affected if The version displayed cannot be compared to a patched version because no safe version range was provided in the CVE description
  3. Identify accessible plugin endpoints
    Review the plugin directory structure (typically in wp-content/plugins/[plugin-folder]/) for PHP files handling admin actions, AJAX endpoints, or API routes. Common locations include files with names like 'admin.php', 'ajax.php', 'api.php', or files in an 'includes' or 'controllers' subfolder.
    Affected if The plugin contains admin configuration pages, AJAX handlers, or API endpoints that process payment settings without visible capability checks in their code
  4. Inspect plugin files for capability checks
    Examine the main plugin PHP files, particularly those handling form submissions or configuration changes. Search for WordPress capability functions such as 'current_user_can()', 'check_admin_referer()', or 'wp_verify_nonce()' around sensitive operations like saving gateway settings or processing transactions.
    Affected if Files handling payment configuration or sensitive operations lack proper capability verification or contain inconsistent permission checks
  5. Review user roles with administrative access
    In WordPress admin, go to Users > All Users. Identify accounts with Administrator or Editor roles, especially any unfamiliar accounts. Cross-reference with your records to confirm all authorized administrators.
    Affected if Unexpected or unauthorized user accounts exist with administrative-level access to the WordPress site

A defender is affected if the Payment Gateway Pix For GiveWP plugin is installed and any sensitive payment configuration or operations can be accessed or modified without proper WordPress capability verification, regardless of user role.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Payment Gateway Pix For GiveWP to the latest version beyond 2.2.3 to obtain the authorization fix. Review all plugin endpoints and ensure proper capability checks are enforced on administrative and payment processing functions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32425 — 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-32425 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