How severe is CVE-2014-4210?

No CVSS score has been assigned to CVE-2014-4210 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-4210?

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

How do I fix CVE-2014-4210?

No fixed version has been published for CVE-2014-4210 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-2014-4210 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2014-4210, including 4 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-2014-4210?

CVE-2014-4210 has an EPSS (Exploit Prediction Scoring System) score of 94.1%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Which products and versions are affected by CVE-2014-4210?

CVE-2014-4210 affects oracle fusion middleware (2 versions, e.g. 10.0.2, 10.3.6). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2014-4210?

A Nuclei detection template exists for CVE-2014-4210, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2014-4210 published, and has it been updated?

CVE-2014-4210 was published on July 17, 2014 and was last updated on May 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2014-4210

Unspecified vulnerability in the Oracle WebLogic Server component in Oracle Fusion Middleware 10.0.2.0 and 10.3.6.0 allows remote attackers to affect confidentiality via vectors related…

Published

Jul 17, 2014

Updated

May 6, 2026

Affected

0 pkgs

Patched

None yet

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

94.1%probability of exploitation in next 30 days

Very High Risk100th 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 WebLogic Server component in Oracle Fusion Middleware 10.0.2.0 and 10.3.6.0 allows remote attackers to affect confidentiality via vectors related to WLS - Web Services.

Affected Products

1 product · 2 configurations

Application

fusion middlewareoracle

2 versions

10.0.210.3.6

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 WebLogic Server component in Ora…

github.comGithubJan 2020

Unspecified vulnerability in the Oracle WebLogic Server component in Ora…

github.comGithubMar 2017

Unspecified vulnerability in the Oracle WebLogic Server component in Ora…

github.comGithubNov 2020

Unspecified vulnerability in the Oracle WebLogic Server component in Ora…

github.comGithubJul 2020

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-4210 in your stack?

O3 detects CVE-2014-4210 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