Intel

AIKIDO-2026-371604

open-dxp/opendxp is vulnerable to Code Injection

GHSA-x4qf-6c7c-5x5rPublished Sep 23, 2026
September 23, 2026

72

CVE Score

High

Code Injection

Are you affected? Scan for Free

TL;DR

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.

How do I fix this?

Upgrade the open-dxp/opendxp library to the patch version.

Who does this affect?

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.

Versions

1.0.0 - 1.4.1

Fixed in 1.4.2

Background info

open-dxp/opendxp is vulnerable to Code Injection in versions 1.0.0 - 1.4.1.

Get secure today,
quickly and for free.

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.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea