CVE-2024-44903
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 · uneditedSQL Injection can occur in the SirsiDynix Horizon Information Portal (IPAC20) through 3.25_9382; however, a patch is available from the vendor. This is in ipac.jsp in a SELECT WHERE statement, in a part of the uri= variable in the second part of the full= inner variable.
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 SirsiDynix Horizon Information Portal (IPAC20) through version 3.25_9382. The vulnerability exists in ipac.jsp within a SELECT WHERE statement, specifically in the uri= variable nested within the full= parameter. An attacker can inject malicious SQL code through this parameter to access, modify, or delete database contents.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 SirsiDynix Horizon Information Portal installationLocate the IPAC20 application in the web server's document root or application server. Look for the ipac.jsp file or the /ipac/ directory structure typically deployed with Horizon IPAC.Affected if SirsiDynix Horizon Information Portal (IPAC20) is installed and the ipac.jsp file exists in the web application directory
-
Determine the installed versionCheck the version metadata within the IPAC20 application. This may be found in a version file, the application header/footer, or configuration files shipped with the installation. Compare against 3.25_9382.Affected if The installed version is 3.25_9382 or any earlier version number
-
Verify ipac.jsp is web-accessibleAttempt to access the ipac.jsp endpoint via HTTP/HTTPS from a client system (e.g., https://[server]/ipac/ipac.jsp). Confirm the page loads and accepts parameters.Affected if The ipac.jsp file is accessible over the network and responds to requests
-
Check for full parameter exposureInspect web request logs or capture traffic to observe whether the full= parameter is being passed to ipac.jsp in normal operation, or test the endpoint by submitting a request with full= parameter.Affected if The full= parameter is accepted and processed by the ipac.jsp endpoint
If the Horizon Information Portal version is 3.25_9382 or earlier and the ipac.jsp with the full parameter is accessible, the environment is vulnerable to SQL injection.
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 dataApply the vendor-provided patch immediately to address the SQL injection vulnerability. If patching is delayed, implement input validation and consider web application firewall (WAF) rules as a temporary compensating control.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44903 — 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-2024-44903 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