CVE-2024-55555: invoiceninja · n/a
Affects invoiceninjaSource CVE Database V5
Not known to be exploited · public exploit available (Metasploit) · CVSS 8.8 High : upgrade to 5.10.43 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 6.6% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.10.43
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade invoiceninja/invoiceninja to 5.10.43.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubinvoiceninja/invoiceninjapkg:github/invoiceninja/invoiceninjaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade all Invoice Ninja installations to version 5.10.43 or later, where this vulnerability is patched. 2. Audit all .env files and configuration repositories to ensure APP_KEY values are unique, secret, and never use default or publicly known keys. 3. Remove any publicly accessible .env files or configuration files from webroot or public repositories. 4. Implement strict access controls on configuration files and environment variables to prevent unauthorized access. 5. Monitor web server logs for suspicious access to the /route/{hash} endpoint and unusual decrypt or unserialize activity. 6. Consider implementing Web Application Firewalls (WAFs) with custom rules to detect and block malformed serialized payloads targeting this route. 7. Educate development and operations teams about the risks of insecure deserialization and the importance of secure key management. 8. Regularly scan for exposed secrets in code repositories and infrastructure using automated secret detection tools. 9. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. 10. Conduct penetration testing and code reviews focusing on deserialization and cryptographic key management practices.
Description
Invoice Ninja before 5.10.43 allows remote code execution from a pre-authenticated route when an attacker knows the APP_KEY. This is exacerbated by .env files, available from the product's repository, that have default APP_KEY values. The route/{hash} route defined in the invoiceninja/routes/client.php file can be accessed without authentication. The parameter {hash} is passed to the function decrypt that expects a Laravel ciphered value containing a serialized object. (Furthermore, Laravel contains several gadget chains usable to trigger remote command execution from arbitrary deserialization.) Therefore, an attacker in possession of the APP_KEY is able to fully control a string passed to an unserialize function.