dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-9021

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
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 6 weeks old

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
The Easy Invoice plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.1.19. This is due to the plugin registering the easy_invoice_accept_quote and easy_invoice_decline_quote AJAX actions via wp_ajax_nopriv_ hooks and relying solely on a quote-scoped nonce that is rendered into the publicly accessible single quote template, combined with an ownership check that is gated behind an off-by-default Pro option (easy_invoice_pro_restrict_quote_to_client). This makes it possible for unauthenticated attackers to accept or decline arbitrary published quotes — and, depending on the configured accept action, automatically convert them into invoices (and even email them to the client) — by harvesting the per-quote nonce from the public quote page and submitting it to admin-ajax.

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 confidence

The Easy Invoice WordPress plugin (versions up to 2.1.19) has a missing authorization vulnerability where AJAX actions for accepting/declining quotes are registered with wp_ajax_nopriv_ hooks, making them accessible to unauthenticated users. The plugin relies on a nonce rendered in public quote pages combined with an ownership check that is disabled by default (Pro feature), allowing unauthenticated attackers to accept or decline arbitrary quotes by harvesting the nonce from public pages.

MitigationRestrict the AJAX endpoints to authenticated users only, enforce the ownership check regardless of Pro settings, and implement proper capability checks before allowing quote status modifications.

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 Easy Invoice plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Easy Invoice' (or 'Easy Invoice - WordPress Invoicing')\n\nAlternatively, check the plugin file: /wp-content/plugins/easy-invoice/readme.txt for the Version header, or query the database wp_options table for option_name 'easy_invoice_version'
    Affected if Plugin is installed and version is 2.1.19 or lower (up to and including 2.1.19)
  2. Confirm AJAX endpoints accept unauthenticated requests
    Send a GET request to your site's wp-admin/admin-ajax.php?action=eas_invoice_accept_quote (or similar endpoint names: eas_invoice_accept_quote, eas_invoice_decline_quote)\n\nExample using curl: curl -s -o /dev/null -w '%{http_code}' https://yourdomain.com/wp-admin/admin-ajax.php?action=eas_invoice_accept_quote
    Affected if HTTP response is 200 (not 403 or 400) indicating the endpoint is accessible without authentication
  3. Verify nonce is exposed on public quote pages
    Visit a public quote page generated by the plugin (typically a URL containing /quote/ or /invoice/ with a quote ID)\n\nView the page source and search for 'eas_invoice_accept_quote' or 'eas_invoice_nonce' to locate the nonce value rendered in the HTML
    Affected if A nonce value is rendered in the HTML of a publicly accessible quote page, allowing attackers to harvest it
  4. Check if ownership verification is enforced
    In WordPress admin, navigate to Easy Invoice settings (usually under 'Easy Invoice' menu)\n\nLook for a 'Pro' or 'Ownership Check' setting - the summary indicates this check is disabled by default and is a Pro feature
    Affected if Ownership verification/check is disabled (Pro feature not active), allowing any user with a valid nonce to modify any quote rather than only their own

Your environment is affected if the Easy Invoice plugin (versions up to 2.1.19) is installed, unauthenticated AJAX requests to quote accept/decline endpoints return 200, and ownership verification is disabled (Pro not active), enabling unauthenticated attackers to manipulate any quote by harvesting the exposed nonce from public pages.

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

Restrict the AJAX endpoints to authenticated users only, enforce the ownership check regardless of Pro settings, and implement proper capability checks before allowing quote status modifications.

Recommended fix Moderate confidence

2.1.20 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Easy Invoice plugin
  4. 4. Check the current version number to confirm it is 2.1.19 or below
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/easy-invoice and upload it manually
  7. 7. After updating, verify that the wp_ajax_nopriv_ hooks for easy_invoice_accept_quote and easy_invoice_decline_quote are either removed or properly protected with authentication checks
  8. 8. Confirm that the Pro option 'easy_invoice_pro_restrict_quote_to_client' is enabled if client-specific quote restrictions are needed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

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