CVE-2025-1537
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 was found in Harpia DiagSystem 12. It has been rated as critical. This issue affects some unknown processing of the file /diagsystem/PACS/atualatendimento_jpeg.php. The manipulation of the argument codexame leads to sql injection. The attack may 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 · moderate confidenceSQL injection vulnerability in Harpia DiagSystem 12's /diagsystem/PACS/atualatendimento_jpeg.php file allows remote attackers to manipulate the codexame parameter to inject arbitrary SQL queries. The exploit is publicly available and the vendor has not responded to disclosure.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Harpia DiagSystem 12 installationCheck your system for Harpia DiagSystem 12 by looking for installation directories, version files, or running services associated with this product. Look for documentation, license files, or service entries referencing DiagSystem.Affected if Harpia DiagSystem 12 is installed and running in your environment
-
Locate the vulnerable PHP fileSearch for the file atualatendimento_jpeg.php in the /diagsystem/PACS/ directory under your web root. This file is part of the PACS (Picture Archiving and Communication System) module.Affected if The file /diagsystem/PACS/atualatendimento_jpeg.php exists in your web application directory
-
Verify PACS module accessibilityConfirm that the /diagsystem/PACS/ endpoint is accessible from your web server. Check your web server configuration and routing to determine if this module is publicly or internally exposed.Affected if The /diagsystem/PACS/ path is accessible via HTTP/HTTPS requests
-
Review codexame parameter handlingExamine the actual PHP code in atualatendimento_jpeg.php. Look specifically at how the codexame parameter is processed - whether it is used directly in SQL queries or passed through prepared statements/parameterized queries.Affected if The code shows the codexame parameter being concatenated directly into SQL queries without using prepared statements or input sanitization
You are affected if Harpia DiagSystem 12 is installed, the vulnerable PHP file exists, the PACS module is accessible, and the codexame parameter is handled without parameterized 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 dataImplement parameterized queries or prepared statements for the codexame parameter and all user-supplied inputs. Conduct input validation and consider Web Application Firewall deployment as an interim control while awaiting vendor patch.
- 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-1537 — 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-1537 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