CVE-2006-7138 json
SQL injection vulnerability in wwv_flow_utilities.gen_popup_list in the WWV_FLOW_UTILITIES package for Oracle APEX/HTMLDB before 2.2 allows…
published 2007-03-07 19 y ago modified 2026-06-16 4 mo ago also EUVD-2006-7120
- cvss
- 6.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
SQL injection vulnerability in wwv_flow_utilities.gen_popup_list in the WWV_FLOW_UTILITIES package for Oracle APEX/HTMLDB before 2.2 allows remote authenticated users to execute arbitrary SQL by modifying the P_LOV parameter and calculating a matching MD5 checksum for the P_LOV_CHECKSUM parameter. NOTE: it is likely that this issue is subsumed by CVE-2006-5351, but due to lack of details from Oracle, this cannot be proven.
Patch / fix
Exploit prediction
1.32% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- lists.grok.org.uk http://lists.grok.org.uk/pipermail/full-disclosure/2006-October/050265.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
red-database-security.com
/advisory/oracle_cpu_oct_2006.html
patch
-
red-database-security.com
/advisory/oracle_apex_sql_injection_wwv_flow_utilities.html
patch
-
lists.grok.org.uk
/pipermail/full-disclosure/2006-October/050265.html
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/30106
vdb-entry
-
securityfocus.com
/archive/1/449498/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/2346
third-party-advisory
Sources
- CVE List CVE-2006-7138
- NVD CVE-2006-7138
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.