How severe is CVE-2018-14667?

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

Which packages are affected by CVE-2018-14667?

CVE-2018-14667 affects the following packages: org.richfaces:richfaces-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-14667?

Update org.richfaces:richfaces-core to 3.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14667 is resolved across your whole dependency graph.

How do I detect CVE-2018-14667 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.richfaces:richfaces-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-14667 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2018-14667 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2018-14667, 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-2018-14667?

CVE-2018-14667 has an EPSS (Exploit Prediction Scoring System) score of 74.2%, placing it in the 99th 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.

Is CVE-2018-14667 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-14667 (Red Hat JBoss RichFaces Framework Expression Language Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-09-28. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-10-19. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2018-14667?

CVE-2018-14667 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-14667 published, and has it been updated?

CVE-2018-14667 was published on May 13, 2022 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2018-14667 — richfaces-core

CRITICALFix: richfaces/richfaces@1372eb7

CVE-2018-14667 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.richfaces:richfaces-core. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-09-28) — treat it as actively exploited and patch now. A fix is available for org.richfaces:richfaces-core — see the affected versions and patch details below.

Richfaces vulnerable to arbitrary code execution

Published

May 13, 2022

Updated

Oct 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

7 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-09-28. Federal agencies were required to remediate by 2023-10-19.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2018-14667.

EPSS Exploitation Probability

via FIRST.org ↗

74.2%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2018-14667 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.richfaces:richfaces-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The RichFaces Framework 3.X through 3.3.4 is vulnerable to Expression Language (EL) injection via the UserResource resource. A remote, unauthenticated attacker could exploit this to execute arbitrary code using a chain of java serialized objects via org.ajax4jsf.resource.UserResource$UriData.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.richfaces:richfaces-core`	all versions	3.3.4`org.richfaces:richfaces-core:3.3.4`

Affected Products

2 products · 3 configurations

enterprise linuxredhat

2 versions

5.06.0

Application

richfacesredhat

≥ 3.1.0 && ≤ 3.3.4

range

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.

The RichFaces Framework 3.X through 3.3.4 is vulnerable to Expression La…

slideshare.netAwesomePocJun 2020

The RichFaces Framework 3.X through 3.3.4 is vulnerable to Expression La…

github.comGithubNov 2018

The RichFaces Framework 3.X through 3.3.4 is vulnerable to Expression La…

github.comGithubSep 2019

The RichFaces Framework 3.X through 3.3.4 is vulnerable to Expression La…

cisa.govCISASep 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.richfaces:richfaces-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.richfaces:richfaces-core to 3.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14667 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Product	Fixed in	Advisory
JBoss Enterprise BRMS Platform 5.3	`RichFaces`	RHSA-2018:3581
Red Hat JBoss EAP 5	`RichFaces`	RHSA-2018:3518
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`richfaces-0:3.3.1-9.SP3_patch_03.ep5.el5`	RHSA-2018:3517
Red Hat JBoss SOA Platform 5.3	`RichFaces`	RHSA-2018:3519

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-14667 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H

CWE Classification

CWE-94Code Injection

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

richfaces

1.2/10

Maintained0/10

Code-Review0/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

First exploit

Jun 26, 2020

Disclosed

May 13, 2022

KEV added

Sep 28, 2023

Last updated

Oct 22, 2025

Identifiers

CVE-2018-14667

References

Advisorynvd.nist.gov Webgithub.com Webaccess.redhat.com Webaccess.redhat.com Webaccess.redhat.com Webaccess.redhat.com Webbugzilla.redhat.com Webcisa.gov Webpacketstormsecurity.com Webseclists.org

Related vulnerabilities

Also affects richfaces-core

This CVE is critical severity, in line with the other 2 CVEs affecting richfaces-core.

CVE-2018-12532CVE-2018-12533

Same weakness: CWE-94

This CVE is critical severity; 1 of 6 other CVEs with CWE-94 is rated as high or higher (top: critical).

CVE-2026-113718CVE-2026-115895CVE-2026-114126CVE-2026-113776CVE-2026-114125CVE-2026-112949Browse all CWE-94

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 22, 2025

CVE-2018-14667 — richfaces-core

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2018-14667 in your dependencies?