Skip to content
Noroxi

Sprout Invoices – Client Invoicing & Estimates

sprout-invoices · plugin

Known security vulnerabilities for Sprout Invoices – Client Invoicing & Estimates. Find out in seconds which version runs on your site with WP Lens.

9 known vulnerabilities

1 critical · 5 exploitable without logging in · latest Sep 30, 2026

Listed on wordpress.org · latest 20.8.18 · last updated Sep 23, 2026 · 1K+ installs

wordpress.org status checked on Oct 2, 2026

Vulnerabilities

  • CVE-2025-64227unauthenticated≤ 20.8.7

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.7 - PHP Object Injection vulnerability

    Critical 9.8
  • CVE-2026-32401high privilege≤ 20.8.9

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.9 - Local File Inclusion vulnerability

    High 7.2
  • CVE-2026-57418login required≤ 20.8.13

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.13 - Broken Access Control vulnerability

    Medium 6.5
  • CVE-2025-24606login required≤ 20.8.1

    WordPress Client Invoicing by Sprout Invoices – Easy Estimates and Invoices for WordPress plugin <=20.8.1 - Broken Access Control vulnerability

    Medium 6.4
  • CVE-2026-97078unauthenticated≤ 20.8.17

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.17 - Insecure Direct Object References (IDOR) vulnerability

    Medium 5.3
  • CVE-2026-39562unauthenticated≤ 20.8.10

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.10 - Broken Access Control vulnerability

    Medium 5.3
  • CVE-2026-25364unauthenticated≤ 20.8.8

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.8 - Broken Access Control vulnerability

    Medium 5.3
  • CVE-2024-53819unauthenticated≤ 20.8.0

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.0 - Insecure Direct Object References (IDOR) vulnerability

    Medium 5.3
  • CVE-2025-64229login required≤ 20.8.7

    WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.7 - Broken Access Control vulnerability

    Medium 4.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory