Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112138 Overview
CVE-2026-112138 is a path traversal vulnerability [CWE-22] in the diem-project diem content management framework through version 5.1.3. The flaw resides in the dmOs::join function within dmFrontPlugin/modules/dmCodeEditor/actions/actions.class.php, part of the dmCodeEditor component. An authenticated attacker can manipulate input to the function and reference files outside the intended directory. The attack is reachable over the network. A public exploit has been disclosed, and the project has not responded to the upstream issue report at the time of publication.
Critical Impact
Authenticated remote attackers can traverse the file system through the dmCodeEditor module and access or modify files outside the intended working directory.
Affected Products
- diem-project diem versions up to and including 5.1.3
- Component: dmFrontPlugin/modules/dmCodeEditor
- Function: dmOs::join
Discovery Timeline
- 2026-10-19 - CVE-2026-112138 published to NVD
- 2026-10-19 - Last updated in NVD database
- An upstream issue was filed in the project repository (GitHub Issue #451); the project has not responded.
Technical Details for CVE-2026-112138
Vulnerability Analysis
The vulnerability exists in the dmCodeEditor module, which exposes an in-application code editor used by privileged users to manage project files. The action handler in actions.class.php passes user-controlled path components into dmOs::join without sufficient normalization or containment checks. As a result, path segments such as ../ are preserved when the resulting path is used for file read or write operations.
Exploitation requires a valid authenticated session with high privileges, since dmCodeEditor is intended for administrative use. Once authenticated, an attacker crafts requests that resolve outside the editor's base directory. Depending on how the resolved path is consumed, impact includes disclosure of configuration files, modification of source files served by the application, and secondary code execution if attacker-controlled content lands in a path interpreted by the PHP runtime.
Root Cause
The root cause is improper limitation of a pathname to a restricted directory [CWE-22]. The dmOs::join helper concatenates path segments without rejecting traversal sequences or validating that the resulting canonical path remains within the intended base directory.
Attack Vector
The attack vector is network-based through the application's HTTP interface. An authenticated user with access to the dmCodeEditor module submits a crafted file or directory parameter containing traversal sequences. The server-side action joins the user input with a trusted base path and performs the file operation against the resolved location. No user interaction beyond the authenticated request is required.
A public proof of concept has been referenced in the VulDB entry (VulDB CVE-2026-112138). No synthetic exploit code is reproduced here; see the referenced advisory for technical specifics.
Detection Methods for CVE-2026-112138
Indicators of Compromise
- HTTP requests to dmCodeEditor action endpoints containing ../, ..%2f, %2e%2e/, or absolute path prefixes in file or directory parameters.
- Unexpected read or write access to files outside the diem project document root originating from the PHP worker process.
- New or modified PHP files in template, cache, or configuration directories that do not match deployment pipeline activity.
Detection Strategies
- Enable verbose access logging on the web server and alert on dmCodeEditor requests containing traversal patterns in query strings or POST bodies.
- Monitor the PHP process for file I/O to paths outside the diem installation root using host-based file integrity monitoring.
- Correlate authenticated administrative sessions with file-system write events to detect misuse of the editor module.
Monitoring Recommendations
- Centralize web server, PHP-FPM, and OS audit logs for the diem host and retain them for incident reconstruction.
- Alert on repeated 4xx or 5xx responses from dmCodeEditor endpoints, which can indicate exploitation attempts and probing.
- Review administrative account activity for logins from unexpected source IP addresses or at unusual times.
How to Mitigate CVE-2026-112138
Immediate Actions Required
- Restrict access to the diem administrative interface and the dmCodeEditor module to trusted networks using firewall or reverse-proxy ACLs.
- Audit and reduce the number of accounts with permission to use dmCodeEditor; remove privileges that are not operationally required.
- Rotate credentials for any administrative account that may have been exposed, and review session tokens.
Patch Information
No vendor patch is available at the time of publication. The project maintainers have not responded to the upstream issue report. Monitor the diem-project repository and GitHub Issue #451 for updates, and review the VulDB entry for additional technical references.
Workarounds
- Disable or remove the dmCodeEditor module from production deployments where it is not required.
- Deploy a web application firewall rule that blocks requests to dmCodeEditor paths containing .., encoded traversal sequences, or absolute path prefixes.
- Run the PHP worker under a restricted operating system user with read and write access limited to the application's data directories, reducing the blast radius of traversal.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

