How severe is CVE-2012-1710?

CVE-2012-1710 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2012-1710?

Affected package information for CVE-2012-1710 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2012-1710?

No fixed version has been published for CVE-2012-1710 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2012-1710 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2012-1710, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2012-1710?

CVE-2012-1710 has an EPSS (Exploit Prediction Scoring System) score of 40.8%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2012-1710 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2012-1710 (Oracle Fusion Middleware Unspecified Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-15. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2012-1710?

CVE-2012-1710 affects oracle fusion middleware (1 version, e.g. 10.1.3.5). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-1710 published, and has it been updated?

CVE-2012-1710 was published on May 3, 2012 and was last updated on April 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-05-25 — agencies required to remediate by 2022-06-15 · Ransomware

CVE-2012-1710

CRITICAL

Unspecified vulnerability in the Oracle WebCenter Forms Recognition component in Oracle Fusion Middleware 10.1.3.5 allows remote attackers to affect confidentiality, integrity, and…

Published

May 3, 2012

Updated

Apr 21, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

40.8%probability of exploitation in next 30 days

High Risk97th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Unspecified vulnerability in the Oracle WebCenter Forms Recognition component in Oracle Fusion Middleware 10.1.3.5 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Designer, a different vulnerability than CVE-2012-1709.

Affected Products

1 product · 1 configurations

Application

fusion middlewareoracle

1 version

10.1.3.5

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Unspecified vulnerability in the Oracle WebCenter Forms Recognition comp…

cisa.govCISAMay 2022

Unspecified vulnerability in the Oracle WebCenter Forms Recognition comp…

proofpoint.comAPIAug 2015

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-1710 in your stack?

O3 detects CVE-2012-1710 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works