CVE-2026-45779
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 · uneditedOpenXDMoD is an open framework for collecting and analyzing HPC metrics. An SQL injection vulnerability exists in Open XDMoD versions prior to 10.0.3 that allows an unauthenticated remote attacker to execute arbitrary SQL statements. Exploitation requires no authentication or user interaction and can result in complete compromise of the underlying database. All deployments of Open XDMoD prior to 10.0.3 are impacted. This issue was discovered on 2023-08-03 and patched on 2023-08-04. At this time there is no evidence that this vulnerability has been exploited in the wild. The vulnerability was patched in Open XDMoD 10.0.3 on 2023-08-04. As a workaround, apply the patch manually.
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 Open XDMoD versions prior to 10.0.3 allows unauthenticated remote attackers to execute arbitrary SQL statements via unsanitized input, potentially leading to complete compromise of the underlying database and the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 OpenXDMoD is installedCheck if OpenXDMoD web application exists in your environment by looking for the application directory or the login page at your configured web server endpoint (typically /xdmod or /open_xdmod).Affected if OpenXDMoD is present in the environment
-
Identify installed OpenXDMoD versionLocate the version file or check the admin interface Help > About page for the installed version number. Common locations include version.php files or the database configuration.Affected if The version is below 10.0.3 (e.g., 10.0.0, 9.5.x, 9.0.x, etc.)
-
Verify web-facing accessibilityDetermine if the OpenXDMoD web interface is accessible from unauthenticated network locations by reviewing firewall rules and web server configuration.Affected if The application is exposed to unauthenticated network access without additional access controls
-
Inspect web server access logs for SQL injection indicatorsReview web server access logs (typically Apache access.log or Nginx access.log) for unusual SQL syntax patterns in request parameters, especially in login, search, or filter endpoints.Affected if Logs contain suspicious SQL commands or unexpected database error messages in requests from unauthenticated sources
-
Audit database for unauthorized changesQuery the database for unexpected modifications such as new administrative users, altered permissions, or suspicious data changes that may indicate successful exploitation.Affected if Database contains unauthorized changes or unexpected records
The environment is affected if OpenXDMoD version is below 10.0.3 and the web interface is accessible to unauthenticated users, as the SQL injection flaw can be exploited remotely without credentials.
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.
dbcve · scoped10.0.3
Upgrade to Open XDMoD version 10.0.3 or later, or manually apply the vendor-provided patch to remediate the SQL injection vulnerability.
10.0.3
- Back up the existing Open XDMoD database and configuration files before proceeding with the upgrade
- Stop any running XDMoD services to prevent data corruption during upgrade
- Download Open XDMoD version 10.0.3 from the official repository or release page
- Extract the new version to the appropriate installation directory
- Run the database upgrade scripts provided in the 10.0.3 release (typically found in the 'tests' or 'setup' directory)
- Start the XDMoD services and verify they are running correctly
- Confirm the SQL injection vulnerability is resolved by reviewing the patch commit referenced in GHSA-r33r-6g3c-r992
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45779 — 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-2026-45779 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