dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-3579

CRITICAL · 9.3 CVSS v4.0 Published 2025-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In versions prior to Aidex 1.7, an authenticated malicious user, taking advantage of an open registry, could execute unauthorised commands within the system. This includes executing operating system (Unix) commands, interacting with internal services such as PHP or MySQL, and even invoking native functions of the framework used, such as Laravel or Symfony. This execution is achieved by Prompt Injection attacks through the /api/<string-chat>/message endpoint, manipulating the content of the ‘content’ parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A prompt injection vulnerability in Aidex versions prior to 1.7 allows authenticated users to execute unauthorized OS commands, interact with internal services (PHP/MySQL), and invoke framework native functions (Laravel/Symfony) by manipulating the 'content' parameter in the /api/<string-chat>/message endpoint.

MitigationUpgrade to Aidex 1.7 or later; implement strict input validation and sanitization on the 'content' parameter; enforce least-privilege authentication and review registry access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Aidex installation and version
    Locate the Aidex installation directory and check the version file (typically version.php, composer.json, or a dedicated version info file in the application root). Compare the installed version number to the affected range (versions prior to 1.7).
    Affected if Installed Aidex version is less than 1.7
  2. Verify the vulnerable API endpoint exists
    Check if the /api/<string-chat>/message endpoint is present in the Aidex installation by examining the routing configuration or attempting a local request to the endpoint path.
    Affected if The /api/<string-chat>/message endpoint exists and responds to requests
  3. Confirm authentication is enforced on the endpoint
    Review the authentication middleware or route configuration for the /api/<string-chat>/message endpoint to verify that unauthenticated requests are rejected.
    Affected if The endpoint accepts requests without requiring valid authentication credentials
  4. Check input validation on the content parameter
    Examine the request handling code for the message endpoint to determine if the 'content' parameter undergoes sanitization, validation, or input filtering before processing.
    Affected if No input validation, sanitization, or filtering is performed on the 'content' parameter before it is processed

A user is affected if Aidex version is less than 1.7, the /api/<string-chat>/message endpoint is accessible, and the 'content' parameter lacks proper input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Aidex 1.7 or later; implement strict input validation and sanitization on the 'content' parameter; enforce least-privilege authentication and review registry access controls.

Recommended fix Moderate confidence

Aidex 1.7

  1. 1. Backup the current Aidex installation and database before proceeding with the upgrade.
  2. 2. Download Aidex version 1.7 or later from the official vendor repository.
  3. 3. Stop the currently running Aidex service.
  4. 4. Replace the existing Aidex files with the new version 1.7 files.
  5. 5. Run any provided database migration scripts included in the upgrade package.
  6. 6. Restart the Aidex service.
  7. 7. Verify the /api/<string-chat>/message endpoint now properly sanitizes the 'content' parameter and prevents prompt injection attacks.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3579 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data