CVE-2026-3461
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 Visa Acceptance Solutions plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 2.1.0. This is due to the `express_pay_product_page_pay_for_order()` function logging users in based solely on a user-supplied billing email address during guest checkout for subscription products, without verifying email ownership, requiring a password, or validating a one-time token. This makes it possible for unauthenticated attackers to log in as any existing user, including administrators, by providing the target user's email address in the billing_details parameter, resulting in complete account takeover and site compromise.
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 Visa Acceptance Solutions WordPress plugin has a critical authentication bypass in the express_pay_product_page_pay_for_order() function. During guest checkout for subscription products, the function accepts any billing email address from the billing_details parameter and automatically logs in as the corresponding user account without verifying ownership, requiring a password, or validating a one-time token, enabling complete account takeover.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 plugin installationInspect WordPress plugins directory for visa-acceptance-solutions folder, or run: wp plugin list --allow-root 2>/dev/null | grep -i visaAffected if The Visa Acceptance Solutions plugin is present in the WordPress installation
-
Determine installed versionRead the plugin header from the main PHP file (e.g., /wp-content/plugins/visa-acceptance-solutions/visa-acceptance-solutions.php) for Version: tag, or query via WP-CLI: wp plugin get visa-acceptance-solutions --field=version --allow-rootAffected if Version is unpatched - compare against vendor release notes for the version that added email ownership verification
-
Check if guest checkout is enabledReview plugin settings page in WordPress admin under WooCommerce > Settings > Visa Acceptance Solutions, or inspect database options table for guest_checkout_enabled or similar flagsAffected if Guest checkout functionality is enabled for subscription products
-
Inspect the vulnerable functionExamine the express_pay_product_page_pay_for_order() function in the plugin source code for billing_details parameter handling - look for missing email verification, password check, or OTP validation before user loginAffected if The function accepts billing email from billing_details and calls wp_signon or similar without ownership verification
User is affected if the Visa Acceptance Solutions plugin is installed with an unpatched version AND guest checkout for subscription products is enabled, allowing the billing_details parameter to authenticate as any user without 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 dataImmediately update the plugin to a patched version that implements proper email ownership verification (e.g., email confirmation link, OTP, or password requirement). Until then, disable the plugin or restrict access to the checkout functionality.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3461 — 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-3461 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