CVE-2025-1156
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 · uneditedA vulnerability has been found in Pix Software Vivaz 6.0.10 and classified as critical. This vulnerability affects unknown code of the file /servlet?act=login. The manipulation of the argument usuario leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceSQL injection vulnerability in Pix Software Vivaz 6.0.10 login function (/servlet?act=login). The 'usuario' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL statements. The exploit is publicly available and trivially exploitable.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify Pix Software Vivaz installationLocate the Vivaz application installation directory, typically found in web server document roots or application directories. Look for the Vivaz software components.Affected if Pix Software Vivaz is installed on the system
-
Verify the installed versionCheck the application version information, typically available in the software itself, an about page, or configuration files. Compare your installed version to 6.0.10.Affected if The installed version is 6.0.10
-
Confirm the login endpoint existsAccess the URL /servlet?act=login or equivalent login path in your environment. Verify the endpoint responds to login requests.Affected if The /servlet?act=login endpoint is accessible and functional
-
Test the usuario parameter for input handlingSubmit login requests with special SQL characters in the 'usuario' parameter (such as quotes, OR statements, or UNION clauses) and observe the application response. Look for database errors, unusual behavior, or successful authentication bypass.Affected if The application returns database error messages or behaves unexpectedly with SQL injection payloads in the usuario parameter, or authentication can be bypassed
-
Review the login code for parameterized queriesExamine the source code or decompiled classes responsible for the login function. Locate the database query that uses the 'usuario' parameter and verify whether prepared statements or parameterized queries are used.Affected if The login query directly concatenates the usuario parameter into the SQL string without using parameterized queries
If Pix Software Vivaz version 6.0.10 is installed and the /servlet?act=login endpoint accepts user input without parameterized queries, the environment is vulnerable to CVE-2025-1156.
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 dataImplement prepared statements/parameterized queries for the login query and all database interactions. Validate and sanitize all user inputs. Apply least-privilege database accounts. Consider deploying a WAF as an interim control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1156 — 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-1156 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