CVE-2026-29925

CVE-2026-29925 is a high-severity vulnerability in Invoiceninja Invoice Ninja with a CVSS 3.x base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-918.

Key facts

Description

Invoice Ninja v5.12.46 and v5.12.48 is vulnerable to Server-Side Request Forgery (SSRF) in CheckDatabaseRequest.php.

Frequently asked questions

What is CVE-2026-29925?
Invoice Ninja v5.12.46 and v5.12.48 is vulnerable to Server-Side Request Forgery (SSRF) in CheckDatabaseRequest.php.
How severe is CVE-2026-29925?
CVE-2026-29925 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-29925 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-29925?
CVE-2026-29925 primarily affects Invoiceninja Invoice Ninja. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-29925?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-29925 have an EU (EUVD) identifier?
Yes. CVE-2026-29925 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-17150.
When was CVE-2026-29925 published?
CVE-2026-29925 was published on 2026-03-30 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Invoiceninja Invoice Ninja

All CVEs affecting Invoiceninja Invoice Ninja →

Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities

Browse all CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities →