CVE-2026-0649VulnerabilityPublished 7 Jan 2026Updated 23 Feb 2026

CVE-2026-0649: invoiceninja · Server-Side Request Forgery

Affects invoiceninjaSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
invoiceninja	Affected =5.12.0 =5.12.1 =5.12.2 =5.12.3 =5.12.4 =5.12.5 =5.12.6 =5.12.7 =5.12.8 =5.12.9 =5.12.10 =5.12.11 =5.12.12 =5.12.13 =5.12.14 =5.12.15 =5.12.16 =5.12.17 =5.12.18 =5.12.19 =5.12.20 =5.12.21 =5.12.22 =5.12.23 =5.12.24 =5.12.25 =5.12.26 =5.12.27 =5.12.28 =5.12.29 =5.12.30 =5.12.31 =5.12.32 =5.12.33 =5.12.34 =5.12.35 =5.12.36 =5.12.37 =5.12.38	Fixed in–

AI-suggested

To mitigate CVE-2026-0649, organizations should first upgrade InvoiceNinja to a version where this vulnerability is patched once available. In the absence of an official patch, implement strict input validation and sanitization on the company_logo parameter to prevent malicious URLs or payloads. Restrict the server's outbound network access using firewall rules or network segmentation to limit requests only to trusted destinations, thereby reducing the SSRF attack surface. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SSRF patterns targeting the vulnerable endpoint. Monitor logs for unusual outbound requests originating from the InvoiceNinja server. Limit user privileges to the minimum necessary to reduce the risk of high-privilege exploitation. Consider isolating the InvoiceNinja instance in a restricted network zone to prevent access to sensitive internal resources. Finally, maintain vigilant threat intelligence monitoring for any emerging exploit code or vendor advisories.

Description

A security vulnerability has been detected in invoiceninja up to 5.12.38. The affected element is the function copy of the file /app/Jobs/Util/Import.php of the component Migration Import. The manipulation of the argument company_logo leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SSRF vulnerability in InvoiceNinja can have significant consequences for organizations relying on this software for financial and invoicing operations. Attackers with high privileges can exploit this flaw to make unauthorized requests from the vulnerable server to internal or external systems. This can lead to unauthorized access to sensitive internal services, exposure of confidential data, or interaction with cloud metadata services that may reveal credentials or configuration details. Additionally, SSRF can be a stepping stone for lateral movement within a network or for launching further attacks such as remote code execution if combined with other vulnerabilities. The impact is heightened in environments where InvoiceNinja is exposed to the internet or integrated with critical internal systems. The absence of vendor patches and public exploit code increases the urgency for organizations to implement mitigations. Overall, this vulnerability threatens confidentiality and integrity, with a moderate impact on availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:19 UTC

Technical details

References

Community reviews

Related threats