CVE-2026-12415
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 Invoice Generator plugin for WordPress is vulnerable to privilege escalation due to a missing capability check on the pravel_invoice_edit_account() AJAX action in versions up to, and including, 1.0.0. The handler is exposed via wp_ajax_nopriv_pravel_invoice_edit_account, accepts an attacker-controlled user_id and user_email from POST data, and calls wp_update_user() without verifying authentication, ownership, or a nonce. This makes it possible for unauthenticated attackers to change the email address of any user, including administrators, and then trigger WordPress's password reset flow to gain access to the targeted account.
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 Invoice Generator plugin for WordPress exposes an AJAX action (pravel_invoice_edit_account) via wp_ajax_nopriv_, making it accessible to unauthenticated users. This handler accepts user_id and user_email from POST data and calls wp_update_user() without any capability checks, authentication verification, or nonce validation. Attackers can change any user's email (including administrators) and then trigger WordPress's password reset to take over the account.
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.
-
Identify if Invoice Generator plugin is installedCheck the wp-content/plugins directory for a folder containing 'invoice' and 'generator' in the name, or query the wp_options table for the plugin active statusAffected if The Invoice Generator plugin by Pravel (or similar name) is installed and active in WordPress
-
Locate the vulnerable AJAX handler registrationSearch plugin PHP files for 'wp_ajax_nopriv_pravel_invoice_edit_account' or 'add_action.*pravel_invoice_edit_account'Affected if The action 'pravel_invoice_edit_account' is registered with wp_ajax_nopriv_ hook, making it accessible to unauthenticated users
-
Inspect the handler function for capability checksFind the function handling pravel_invoice_edit_account and look for current_user_can() calls, specifically 'edit_users' or similar administrative capabilitiesAffected if The handler function lacks capability checks (e.g., current_user_can('edit_users')) before processing user data
-
Inspect the handler for nonce validationSearch the handler function for wp_verify_nonce(), check_admin_referer(), or nonce field verificationAffected if No nonce validation is performed before allowing user modification
-
Verify the handler accepts user_id and user_email from POSTExamine the handler code for $_POST['user_id'] or $_POST['user_email'] usage passed to wp_update_user()Affected if The handler directly uses user-supplied POST parameters for user_id and user_email in wp_update_user() without ownership verification
-
Confirm unauthenticated access is possibleSend a POST request to /wp-admin/admin-ajax.php with action=pravel_invoice_edit_account and test user modification without authentication cookiesAffected if The AJAX endpoint responds and allows email modification for arbitrary users without being logged in
A user is affected if the Invoice Generator plugin is installed and its pravel_invoice_edit_account AJAX handler is exposed to unauthenticated users without capability checks, nonce validation, or ownership 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 dataAdd a capability check (e.g., current_user_can('edit_users')) and nonce verification to the pravel_invoice_edit_account AJAX handler, and implement ownership verification to ensure users can only modify their own account. Consider restricting the nopriv hook or requiring authentication.
- 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-12415 — 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-12415 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