CVE-2007-5766
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 vulnerability in okxLOV.jsp in Oracle E-Business Suite 11 and 12 allows remote attackers to execute arbitrary SQL commands via unknown vectors. NOTE: this is probably the same issue as CVE-2007-5527 or CVE-2007-5528, but there are insufficient details to be sure.
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 okxLOV.jsp within Oracle E-Business Suite versions 11 and 12 allows remote attackers to execute arbitrary SQL commands by injecting malicious SQL statements through unknown vectors in the JSP page.
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= 11i= 12CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Oracle E-Business Suite installationCheck the application version by querying the Oracle database or checking the installation directory for E-Business Suite 11i or 12 release files. Use 'adident Header' or check the 'AD_PRODUCT_GROUPS' table for version information.Affected if The environment runs Oracle E-Business Suite version 11i or 12.
-
Locate the okxLOV.jsp fileSearch the application web root directories for the presence of okxLOV.jsp. Common paths include $IAS_ORACLE_HOME/Apache/Apache/htdocs or the web tier document root under 'oa_html' or 'OA_JAVA' directories.Affected if The okxLOV.jsp file exists in the deployed application.
-
Verify web accessibility of the vulnerable JSPTest if okxLOV.jsp is accessible via HTTP/HTTPS by attempting to access it through the web server. Check the web tier configuration and URL patterns to confirm the JSP is publicly or internally reachable.Affected if The okxLOV.jsp endpoint is accessible over the network without authentication barriers.
-
Review request logging for suspicious parametersExamine web server access logs (Apache, Oracle HTTP Server) for requests to okxLOV.jsp containing SQL syntax in query parameters, such as single quotes, UNION SELECT, or common SQL injection patterns.Affected if Logs show requests to okxLOV.jsp with SQL metacharacters in parameters.
A system is affected if it runs Oracle E-Business Suite 11i or 12 with the okxLOV.jsp file deployed and accessible, as this JSP does not sanitize user input before using it in 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 dataApply Oracle's relevant security patches for E-Business Suite; until patches are available, restrict network access to affected E-Business Suite endpoints and implement web application firewall rules to detect and block SQL injection attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5766 — 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-2007-5766 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