cjbi admin3 up to 3.0.0 Audit Log C02_log_session_token_disclosure.py authentication replay

Summaryinfo

A vulnerability labeled as critical has been found in cjbi admin3 up to 3.0.0. This issue affects some unknown processing of the file C02_log_session_token_disclosure.py of the component Audit Log. Such manipulation leads to authentication replay. This vulnerability is listed as CVE-2026-92918. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, has been found in cjbi admin3 up to 3.0.0. Affected by this issue is an unknown part of the file C02_log_session_token_disclosure.py of the component Audit Log. The manipulation with an unknown input leads to a authentication replay vulnerability. Using CWE to declare the problem leads to CWE-294. A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-92918 since 09/17/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 09/17/2026). The MITRE ATT&CK project declares the attack technique as T1040.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• cjbi

Name

• admin3

Version

• 3.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion