CVE-2025-56700
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 · uneditedBoolean SQL injection vulnerability in the web app of Base Digitale Group spa product Centrax Open PSIM version 6.1 allows a low level priviliged user that has access to the platform, to execute arbitrary SQL commands via the datafine 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 confidenceBoolean SQL injection vulnerability in the datafine parameter of Centrax Open PSIM v6.1 web interface allows authenticated low-privilege users to inject arbitrary SQL commands via the parameter, potentially exposing or manipulating the underlying database.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Centrax Open PSIM installationLocate the Centrax Open PSIM installation directory or check running services for Centrax PSIM components. Identify the installed version by reviewing application metadata, license files, or version information files typically found in the installation directory.Affected if The installed version matches Centrax Open PSIM v6.1 or falls within the affected version range for this release.
-
Verify web interface is enabledCheck if the Centrax PSIM web interface service is running and accessible. Look for HTTP/HTTPS listeners on common web ports or review service configuration files that expose the web interface.Affected if The web interface is running and reachable, making the datafine parameter accessible for injection attempts.
-
Identify datafine parameter exposureReview web application traffic or enumerate available parameters in web interface forms and URLs. Locate the datafine parameter within the application's request handling for date filtering or data range functions.Affected if The datafine parameter is present and accepts user-supplied input without proper sanitization.
-
Confirm authentication accessibilityVerify that low-privilege user accounts can authenticate to the web interface. Test login with a standard user account that has basic access rights rather than administrative privileges.Affected if Low-privilege authenticated users can access the web interface and reach functionality utilizing the datafine parameter.
-
Test for boolean SQL injectionSubmit a crafted payload to the datafine parameter that uses boolean logic (e.g., '1=1' vs '1=2') in an authenticated request. Compare application responses to determine if SQL syntax is being interpreted by the database.Affected if Different responses are returned for true versus false conditions, confirming the parameter is vulnerable to SQL injection.
A user is affected if running Centrax Open PSIM v6.1 with the web interface enabled, where low-privilege authenticated users can access the datafine parameter and trigger different application behavior based on SQL boolean conditions.
Generated from the published advisory. Verify against your own configuration.
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 dataRemediate by implementing parameterized queries or prepared statements for the datafine parameter and adding proper input validation. Apply vendor patch when available and consider WAF deployment as interim control.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2025-56700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-56700 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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