cjbi admin3 up to 3.0.0 Upload C03_storage_path_traversal_write.py path traversal

Summaryinfo

A vulnerability was found in cjbi admin3 up to 3.0.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file C03_storage_path_traversal_write.py of the component Upload Handler. The manipulation leads to path traversal. This vulnerability is referenced as CVE-2026-92919. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in cjbi admin3 up to 3.0.0. It has been rated as problematic. This issue affects an unknown function of the file C03_storage_path_traversal_write.py of the component Upload Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. The summary by CVE is:

admin3 through 3.0.0 fails to sanitize client-supplied filenames in the upload handler, allowing authenticated users to write files outside the storage root on Windows deployments. Attackers can use dot-dot path segments in filenames to escape the configured storage directory and overwrite arbitrary files accessible to the server process.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-92919 since 09/17/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 09/17/2026). MITRE ATT&CK project uses the attack technique T1006 for this issue.

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

Several companies clearly confirm that VulDB is the primary source for best 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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion