admin3: Insertion of Sensitive Information into Log File
CVE-2026-92918 is a high-severity insertion of sensitive information into log file vulnerability in admin3 from Cjbi, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected admin3 versions: 3.0.0 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.65% chance of exploitation within 30 days, higher than 52% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of admin3 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 8.8 | High | CNA (vulncheck.com) |
Official description
admin3 through 3.0.0 persists user session tokens in the audit log event body when publishing UserLoggedIn domain events. Attackers with log:view permission can read the JSON response from the GET /logs endpoint to harvest session tokens and replay them as bearer credentials for full user access.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How developers prevent this class of flaw
- Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Remove debug log files before deploying the application into production.
- Protect log files against unauthorized read/write.
More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- github.com/LinYuanyi1/cve-request-poc/blob/master/admin3/C02_log_session_token_disclosure.py
- github.com/cjbi/admin3
- github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/java/tech/wetech/admin3/infra/service/DefaultSession…
- github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/java/tech/wetech/admin3/sys/service/LogService.java
- github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/resources/data.sql
- vulncheck.com/advisories/admin3-through-3.0.0-session-token-disclosure-via-audit-log
Other vulnerabilities in admin3
- 8.1 High severity
Recent Insertion of Sensitive Information into Log File vulnerabilities
- 7.1 High severity
- 7.5 High severity
- 7.7 High severity
- 7.7 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.