AJ-Report through 1.7.1 Authentication Bypass leading to RCE via Share-Token
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AJ-Report, a reporting application, is affected by this vulnerability. An attacker can forge access tokens and run arbitrary code on the server without logging in, which could let them fully take over the system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
AJ-Report through 1.7.1 signs share tokens with a hard-coded JWT secret, allowing attackers to forge valid Share-Tokens offline. Attackers can mint a token with reportCode 'dataSet' to access the testTransform endpoint, which passes scripts to GroovyClassLoader for unauthenticated remote code execution.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- anji-plus AJ-Report
through 1.7.1
References 4
Questions about CVE-2026-120209
What does this mean?
An unauthenticated attacker can run arbitrary Groovy or Java code on the server through the share-token feature, with the privileges of the application process (root in the official image). The attacker can also reach all data sources configured in the application, which can enable lateral movement.Source: gitee.com
Am I affected, and how do I check?
The advisory says affected versions are AJ-Report V1.4.2 through V1.7.1. To check a deployment, compare the installed AJ-Report version against that range.Source: gitee.com
What should I do about it?
The checked facts do not list a fixed version, so no upgrade target can be named from them. Check the vendor's advisory for a fixed release before planning an upgrade.Source: gitee.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts give no workaround or fix, so no interim mitigation can be confirmed from them. Check the vendor's advisory for any published interim steps.Source: gitee.com