CVE-2025-1808
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 Pixsoft E-Saphira 1.7.24 and classified as critical. This vulnerability affects unknown code of the file /servlet?act=login&tipo=1 of the component Login Endpoint. The manipulation of the argument txtUsuario 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 Pixsoft E-Saphira 1.7.24 login endpoint (/servlet?act=login&tipo=1) allowing remote attackers to inject arbitrary SQL queries through the txtUsuario parameter.
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 Pixsoft E-Saphira installationSearch for E-Saphira web application files, typically deployed on Java servlet containers (Apache Tomcat, JBoss). Check for directories containing 'esaphira' or 'pixsoft' in the web application root.Affected if The application is present and running on the system
-
Determine installed versionLocate version files or manifest (such as version.txt, MANIFEST.MF, or configuration files in the application WEB-INF directory). Compare the found version to 1.7.24.Affected if Installed version matches or is below 1.7.24 (assuming 1.7.24 is the vulnerable release)
-
Verify vulnerable endpoint existsCheck application web.xml descriptor or URL routing configuration for the /servlet endpoint with act=login and tipo=1 parameters. Inspect if the login servlet is accessible at /servlet?act=login&tipo=1.Affected if The login endpoint /servlet?act=login&tipo=1 is accessible and responds to requests
-
Confirm txtUsuario parameter handlingReview application source code (JSP/servlet files) or decompile the login servlet class. Look for how the txtUsuario parameter is used in SQL queries.Affected if The txtUsuario parameter is concatenated directly into SQL queries without parameterized statements or input sanitization
-
Check for SQL injection vulnerabilityIf authorized and in a non-production environment, send a test request with a single quote in txtUsuario (e.g., txtUsuario=') and observe for SQL error messages in the response or application logs.Affected if The application returns database errors or behaves unexpectedly with SQL injection payloads in txtUsuario
The environment is affected if Pixsoft E-Saphira version 1.7.24 or lower is installed and the /servlet?act=login&tipo=1 endpoint with the txtUsuario parameter is exposed and uses unparameterized SQL queries.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements in the login endpoint, and implement proper input validation for the txtUsuario argument.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1808 — 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-1808 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