dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-56699

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
SQL injection vulnerability in the cmd component of Base Digitale Group spa product Centrax Open PSIM version 6.1 allows an unauthenticated user to execute arbitrary SQL commands via the sender 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 · high confidence

SQL injection vulnerability in the cmd component of Centrax Open PSIM v6.1 allows unauthenticated attackers to execute arbitrary SQL commands through the sender parameter.

MitigationImplement parameterized queries or prepared statements for all database queries using the sender parameter, and apply input validation/sanitization.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 Centrax Open PSIM version
    Locate the installation directory or check the application startup banner/logs for the version number. Common paths include /opt/centrax or check the GUI 'About' section if accessible.
    Affected if Version is 6.1 exactly, or falls within the v6.1.x family where the vulnerability exists
  2. Verify cmd component is enabled
    Check the application configuration files (typically centrax.xml, config.xml, or similar in the installation directory) for the cmd component definition and its enabled status.
    Affected if The cmd component is present and enabled in the configuration
  3. Confirm sender parameter is processed
    Review application logs or intercept HTTP requests to the cmd endpoint. The sender parameter should be visible in request logs or captured via a proxy tool when sending a test request.
    Affected if The sender parameter is accepted and processed by the cmd component endpoint
  4. Check network exposure of cmd endpoint
    Determine if the Centrax Open PSIM web interface or cmd component port is exposed to untrusted networks. Check firewall rules and listen addresses in the application configuration.
    Affected if The cmd endpoint is accessible from untrusted/network-facing interfaces without authentication

The environment is affected if Centrax Open PSIM v6.1 is installed, the cmd component is enabled, and the sender parameter is being processed by an accessible endpoint.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database queries using the sender parameter, and apply input validation/sanitization.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-56699 — 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-56699 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