open-dxp/opendxp is vulnerable to Code Injection
72
CVE Score
High
Code Injection
A backend user holding the classes permission can define a DataObject class whose field name or class name/ID is written unescaped into the generated PHP class file and into ALTER TABLE DDL. Class name/ID validation uses an unanchored identifier regex, so extra characters pass the check, and the class ID is concatenated unquoted into raw SQL table names when loading DataObject field data. A crafted field name reaches arbitrary PHP execution once the generated class file is autoloaded, and a crafted class ID leads to SQL injection. The fix anchors the identifier validation regex to the full name/ID and quotes the constructed table and index identifiers before use.
Upgrade the open-dxp/opendxp library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you hold the classes permission to create or import DataObject class definitions.
1.0.0 - 1.4.1
Fixed in 1.4.2open-dxp/opendxp is vulnerable to Code Injection in versions 1.0.0 - 1.4.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.