JeecgBoot up to 3.9.5 AiragExtDataController poc_airag_extdata_delete_batch.py AiragExtDataController.deleteBatch ids improper authorization

Summaryinfo

A vulnerability has been found in JeecgBoot up to 3.9.5 and classified as problematic. Affected by this vulnerability is the function AiragExtDataController.deleteBatch of the file poc_airag_extdata_delete_batch.py of the component AiragExtDataController. The manipulation of the argument ids leads to improper authorization. This vulnerability is referenced as CVE-2026-108616. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in JeecgBoot up to 3.9.5. This issue affects the function AiragExtDataController.deleteBatch of the file poc_airag_extdata_delete_batch.py of the component AiragExtDataController. The manipulation of the argument ids with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity, and availability. The summary by CVE is:

JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the AiragExtDataController deleteBatch handler that allows any authenticated user to delete AI evaluator records. Low-privileged attackers can send comma-separated ids to DELETE /airag/extData/deleteBatch, which lacks owner or tenant checks, deleting other users' evaluator and test-tracking records.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-108616 since 10/10/2026. The exploitation is known to be easy. The attack may be initiated 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/11/2026). MITRE ATT&CK project uses the attack technique T1548.002 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

• JeecgBoot

Version

• 3.9.0
• 3.9.1
• 3.9.2
• 3.9.3
• 3.9.4
• 3.9.5

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