Erupt up to 2.3.0 /erupt-api/data/table linkTreeVal code injection

Summaryinfo

A vulnerability identified as problematic has been detected in Erupt up to 2.3.0. This affects an unknown part of the file /erupt-api/data/table. Performing a manipulation of the argument linkTreeVal results in code injection. This vulnerability is cataloged as CVE-2026-111390. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Erupt up to 2.3.0. It has been classified as problematic. This affects some unknown functionality of the file /erupt-api/data/table. The manipulation of the argument linkTreeVal with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality. The summary by CVE is:

Erupt through 2.3.0 contains an HQL injection vulnerability that allows authenticated users to bypass tree-scoped data filters by injecting unescaped quotes into the linkTreeVal parameter of POST /erupt-api/data/table/{erupt}. Attackers holding query permission on entities with String-keyed linkTree targets can append always-true OR clauses or boolean subqueries to read data from other mapped entities.

The advisory is shared at hackmd.io. This vulnerability is uniquely identified as CVE-2026-111390 since 10/15/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/16/2026). MITRE ATT&CK project uses the attack technique T1059 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Erupt

Version

• 2.0
• 2.1
• 2.2
• 2.3.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion