dbcve.org
ApexApplication · Oracle

CVE-2007-3860

HIGH · 7.5 CVSS v2.0 Published 2007-07-18
Fix available
A fix is available. Upgrade to after 3.0.0.00.20 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

SQL injection vulnerability in Oracle Application Express wwv_flow_security.check_db_password function due to insufficient validation of single quote characters ('), allowing attackers to inject arbitrary SQL statements.

MitigationApply Oracle Critical Patch Update (July 2007) or later version of Oracle Application Express that addresses this SQL injection in wwv_flow_security.check_db_password.

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
ApexApplication
Affected:<= 3.0.0.00.20= 2.2.0.00.32

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Application Express version
    Connect to the Oracle database and query the Apex version from the flows or apex_release table. Common query: SELECT version FROM apex_release; or SELECT text FROM wwv_flows WHERE flow_name like '%apex%';
    Affected if Version is 2.2.0.00.32 or version is less than or equal to 3.0.0.00.20
  2. Verify Apex installation exists
    Confirm Oracle Application Express is installed by checking for the APEX_030200 (or similar) schema, or by querying user_tables for APEX related objects.
    Affected if Apex schema exists and version falls in affected range
  3. Confirm wwv_flow_security component
    Check that the wwv_flow_security package exists in the database by querying user_objects where object_name = 'WWV_FLOW_SECURITY'.
    Affected if The WWV_FLOW_SECURITY package exists in a version within the affected range

The environment is affected if Oracle Application Express is installed with version 2.2.0.00.32 or any version less than or equal to 3.0.0.00.20.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.0.0.00.20
Interim mitigation

Apply Oracle Critical Patch Update (July 2007) or later version of Oracle Application Express that addresses this SQL injection in wwv_flow_security.check_db_password.

Fix this in Apex Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-3860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-3860 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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