CVE-2025-15400
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 OpenPix for WooCommerce WordPress plugin through 2.13.3 allows any authenticated user to trigger AJAX actions that reset payment gateway configuration options without capability or nonce checks. This permits any authenticated users, such as subscribers to clear API credentials and webhook status, causing persistent disruption of OpenPix payment functionality.
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 OpenPix for WooCommerce plugin through 2.13.3 has a broken access control vulnerability in its AJAX handlers. Any authenticated user (including low-privilege subscribers) can trigger AJAX actions that reset payment gateway configuration options, including clearing API credentials and webhook status, without any capability or nonce verification checks.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify if OpenPix for WooCommerce plugin is installedCheck the WordPress plugins directory or use wp plugin list to see if 'openpix-for-woocommerce' or similar is presentAffected if The plugin is installed and active in WordPress
-
Determine installed plugin versionCheck the plugin header in openpix-for-woocommerce.php or use wp plugin get openpix-for-woocommerce to view version metadataAffected if Version is 2.13.3 or lower (any version through 2.13.3 is affected)
-
Verify existence of low-privilege user accountsQuery the wp_users and wp_usermeta tables or use wp user list --role=subscriber to check for subscriber-level accountsAffected if Any subscriber or low-privilege user accounts exist on the site
-
Inspect AJAX handler registration for capability checksSearch plugin source for add_action( 'wp_ajax_' ) calls and verify if current_user_can() or similar capability checks are present before processing configuration reset actionsAffected if AJAX actions lack capability checks and allow subscriber-level users to reset payment settings
-
Check if AJAX actions lack nonce verificationSearch plugin source for check_ajax_referer() or wp_verify_nonce() calls within AJAX callback functions that handle configuration changesAffected if AJAX handlers processing configuration resets do not verify nonces before executing
A user is affected if they have OpenPix for WooCommerce version 2.13.3 or lower installed AND have any subscriber or low-privilege user accounts on their WordPress site, since those users can exploit the unauthenticated AJAX endpoints to reset payment gateway settings.
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.
dbcve · scopedAdd proper capability checks (using current_user_can()) and nonce verification (using check_ajax_referer() or wp_verify_nonce()) to all AJAX action handlers in the plugin before processing any configuration changes.
latest available version (after 2.13.3)
- Check current installed version of OpenPix for WooCommerce plugin in WordPress admin under Plugins
- Navigate to Plugins > Installed Plugins and locate OpenPix for WooCommerce
- If current version is 2.13.3 or earlier, update the plugin to the latest available version via WordPress admin or upload the latest version from WordPress.org
- After updating, verify the AJAX actions now require proper authorization (nonce) and capability checks
- Confirm payment gateway configuration options cannot be cleared by low-privileged users (subscribers)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15400 — 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-15400 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