Unspecified vulnerability in Oracle Application Express (formerly Oracle HTML DB) 2.2.0.00.32 up to 3.0.0.00.20 allows developers to have an unknown impact via unknown attack vectors, aka APEX01. NOTE: a reliable researcher states that this is SQL injection in the wwv_flow_security.check_db_password function due to insufficient checks for '"' characters.
CVE-2007-3860
NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- 77.9%
- KEV
- Not listed
Published
July 18, 2007
Last Modified
April 23, 2026
References (30)
- cve@mitrehttp://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00727143
- cve@mitrehttp://secunia.com/advisories/26114
- cve@mitrehttp://secunia.com/advisories/26166
- cve@mitrehttp://securityreason.com/securityalert/2901
- cve@mitrehttp://www.integrigy.com/security-resources/analysis/Integrigy_Oracle_CPU_July_2007_Analysis.pdf
- cve@mitrehttp://www.oracle.com/technetwork/topics/security/cpujul2007-087014.html
- cve@mitrehttp://www.red-database-security.com/advisory/oracle_apex_sql_injection_check_db_password.html
- cve@mitrehttp://www.red-database-security.com/advisory/oracle_cpu_jul_2007.html
- cve@mitrehttp://www.securityfocus.com/archive/1/474002/100/0/threaded
- cve@mitrehttp://www.securitytracker.com/id?1018415
- cve@mitrehttp://www.us-cert.gov/cas/techalerts/TA07-200A.html
- cve@mitrehttp://www.vupen.com/english/advisories/2007/2562
- cve@mitrehttp://www.vupen.com/english/advisories/2007/2635
- cve@mitrehttps://exchange.xforce.ibmcloud.com/vulnerabilities/35490
- cve@mitrehttps://exchange.xforce.ibmcloud.com/vulnerabilities/35499
Data Freshness Timeline
(refreshed 3× in last 7d / 37× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 06:07 UTCEPSS rescore
- 2026-07-11 08:22 UTCEPSS rescore
- 2026-07-08 15:09 UTCEPSS rescore
- 2026-07-06 16:22 UTCEPSS rescore
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-05 02:26 UTCEPSS rescore
- 2026-07-04 06:27 UTCEPSS rescore
- 2026-07-04 06:27 UTCEPSS rescore
- 2026-07-02 14:00 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-29 14:02 UTCEPSS rescore
- 2026-06-29 14:02 UTCEPSS rescore
- 2026-06-28 04:52 UTCEPSS rescore
- 2026-06-27 03:04 UTCEPSS rescore
- 2026-06-25 13:46 UTCEPSS rescore
- 2026-06-25 13:46 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:29 UTCEPSS rescore
- 2026-06-23 21:29 UTCEPSS rescore
- 2026-06-22 14:22 UTCEPSS rescore
- 2026-06-21 14:53 UTCEPSS rescore
Show 56 moreShow fewer
- 2026-06-21 01:56 UTCEPSS rescore
- 2026-06-21 01:56 UTCEPSS rescore
- 2026-06-19 19:22 UTCEPSS rescore
- 2026-06-19 19:22 UTCEPSS rescore
- 2026-06-18 17:49 UTCEPSS rescore
- 2026-06-18 17:49 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-16 17:49 UTCEPSS rescore
- 2026-06-16 17:49 UTCEPSS rescore
- 2026-06-16 17:49 UTCEPSS rescore
- 2026-06-15 17:44 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:08 UTCEPSS rescore
- 2026-06-10 22:14 UTCEPSS rescore
- 2026-06-10 13:17 UTCEPSS rescore
- 2026-06-08 14:13 UTCEPSS rescore
- 2026-06-07 15:21 UTCEPSS rescore
- 2026-06-06 13:44 UTCEPSS rescore
- 2026-06-06 13:44 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 06:07 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 01:44 UTCEG score recompute
- 2026-05-31 01:44 UTCGHSA enrichment
- 2026-05-31 00:13 UTCEPSS rescore
- 2026-05-31 00:13 UTCEPSS rescore
- 2026-05-29 13:40 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-27 13:37 UTCEPSS rescore
- 2026-05-27 13:37 UTCEPSS rescore
- 2026-05-26 13:41 UTCEPSS rescore
- 2026-05-26 13:41 UTCEPSS rescore
- 2026-05-24 16:42 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-21 22:38 UTCEPSS rescore
- 2026-05-20 22:36 UTCEPSS rescore
- 2026-05-20 22:36 UTCEPSS rescore
- 2026-05-20 11:20 UTCEPSS rescore
- 2026-05-20 11:20 UTCEPSS rescore
- 2026-05-18 21:29 UTCEPSS rescore
- 2026-05-18 21:29 UTCEPSS rescore
Frequently asked(4)
What is CVE-2007-3860?
CVE-2007-3860 is a none vulnerability published on July 18, 2007. Unspecified vulnerability in Oracle Application Express (formerly Oracle HTML DB) 2.2.0.00.32 up to 3.0.0.00.20 allows developers to have an unknown impact via unknown attack vectors, aka APEX01. NOTE: a reliable researcher states that this is SQL injection in the wwvflowsecurity.checkdbpassword…
When was CVE-2007-3860 disclosed?
CVE-2007-3860 was first published in the National Vulnerability Database on July 18, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-3860 actively exploited?
CVE-2007-3860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 77.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2007-3860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2007-3860, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2007-3860
Is Your Infrastructure Affected by CVE-2007-3860?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.