CVE-2007-5511

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 32%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SQL injection vulnerability in Workspace Manager for Oracle Database before OWM 10.2.0.4.1, OWM 10.1.0.8.0, and OWM 9.2.0.8.0 allows attackers to execute arbitrary SQL commands via the FINDRICSET procedure in the LT package. NOTE: this is probably covered by CVE-2007-5510, but there are insufficient details to be certain.

CVSS v3
EG Score
0.0(none)
EPSS
98.1%
KEV
Not listed

Published

October 17, 2007

Last Modified

April 23, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 31× 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.

  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-08 15:09 UTCEPSS rescore
  3. 2026-07-06 16:22 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-02 14:00 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-27 03:04 UTCEPSS rescore
  12. 2026-06-25 13:46 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:29 UTCEPSS rescore
  17. 2026-06-23 21:29 UTCEPSS rescore
  18. 2026-06-22 14:22 UTCEPSS rescore
  19. 2026-06-21 14:53 UTCEPSS rescore
  20. 2026-06-21 01:56 UTCEPSS rescore
  21. 2026-06-21 01:56 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 41 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-16 17:49 UTCEPSS rescore
  4. 2026-06-15 17:44 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-12 23:08 UTCEPSS rescore
  7. 2026-06-10 22:14 UTCEPSS rescore
  8. 2026-06-10 13:17 UTCEPSS rescore
  9. 2026-06-08 14:13 UTCEPSS rescore
  10. 2026-06-07 15:21 UTCEPSS rescore
  11. 2026-06-05 22:44 UTCEPSS rescore
  12. 2026-06-05 22:44 UTCEPSS rescore
  13. 2026-06-05 06:07 UTCEPSS rescore
  14. 2026-06-04 13:09 UTCEPSS rescore
  15. 2026-06-04 13:09 UTCEPSS rescore
  16. 2026-06-04 13:09 UTCEPSS rescore
  17. 2026-06-02 20:10 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-06-01 13:49 UTCEPSS rescore
  21. 2026-06-01 13:49 UTCEPSS rescore
  22. 2026-05-31 00:28 UTCEG score recompute
  23. 2026-05-31 00:28 UTCGHSA enrichment
  24. 2026-05-31 00:13 UTCEPSS rescore
  25. 2026-05-31 00:13 UTCEPSS rescore
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-27 13:37 UTCEPSS rescore
  32. 2026-05-27 13:37 UTCEPSS rescore
  33. 2026-05-26 07:16 UTCEPSS rescore
  34. 2026-05-26 07:16 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-21 22:38 UTCEPSS rescore
  38. 2026-05-20 22:36 UTCEPSS rescore
  39. 2026-05-20 22:36 UTCEPSS rescore
  40. 2026-05-18 21:29 UTCEPSS rescore
  41. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-4572✓ verified
    First seen Oct 27, 2007

    Oracle 10g - 'LT.FINDRICSET' SQL Injection (IDS Evasion)

    Open source ↗
  • Exploit-DBEDB-4570✓ verified
    First seen Oct 27, 2007

    Oracle 10g/11g - 'SYS.LT.FINDRICSET' SQL Injection (1)

    Open source ↗
  • Exploit-DBEDB-4571✓ verified
    First seen Oct 27, 2007

    Oracle 10g/11g - 'SYS.LT.FINDRICSET' SQL Injection (2)

    Open source ↗
  • Metasploitauxiliary/sqli/oracle/lt_findricset_cursor✓ verified
    First seen Oct 17, 2007

    Oracle DB SQL Injection via SYS.LT.FINDRICSET Evil Cursor Method

    Open source ↗

Frequently asked(4)

What is CVE-2007-5511?
CVE-2007-5511 is a none vulnerability published on October 17, 2007. SQL injection vulnerability in Workspace Manager for Oracle Database before OWM 10.2.0.4.1, OWM 10.1.0.8.0, and OWM 9.2.0.8.0 allows attackers to execute arbitrary SQL commands via the FINDRICSET procedure in the LT package. NOTE: this is probably covered by CVE-2007-5510, but there are…
When was CVE-2007-5511 disclosed?
CVE-2007-5511 was first published in the National Vulnerability Database on October 17, 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-5511 actively exploited?
CVE-2007-5511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2007-5511?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2007-5511, 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-5511

Explore →

Is Your Infrastructure Affected by CVE-2007-5511?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.