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.
CVE-2018-14667
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-09-28), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EPSS
- 99.4%
- KEV
- ⚠ Exploited
Published
November 6, 2018
Last Modified
November 3, 2025
Advisory Details (8)
Auto-updated Jun 1, 2026Full Disclosure: RichFaces exploitation toolkit
http://seclists.org/fulldisclosure/2020/Mar/21Packet Storm
http://packetstormsecurity.com/files/156663/Richsploit-RichFaces-Exploitation-Toolkit.html1639139 – (CVE-2018-14667) CVE-2018-14667 RichFaces: Expression Language injection via UserResource allows for unauthenticated remote code execution
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14667Affected: Red Hat Enterprise Linux 5.
https://access.redhat.com/errata/RHSA-2018:3517Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | RichFaces | 2018-11-13 | redhat |
| redhat | richfaces-0:3.3.1-6.SP3_patch_03.ep5.el6 | 2018-11-06 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.richfaces:richfaces-core | — | 3.3.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(4)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 83× in last 7d / 372× 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.
Showing the most recent 100 of 537 total refreshes for this CVE.
- 2026-07-12 17:48 UTCEG score recompute
- 2026-07-12 17:48 UTCVendor advisory
- 2026-07-12 13:34 UTCEG score recompute
- 2026-07-12 13:34 UTCVendor advisory
- 2026-07-12 09:19 UTCEG score recompute
- 2026-07-12 09:19 UTCVendor advisory
- 2026-07-12 05:04 UTCEG score recompute
- 2026-07-12 05:04 UTCVendor advisory
- 2026-07-12 00:49 UTCEG score recompute
- 2026-07-12 00:49 UTCVendor advisory
- 2026-07-11 20:35 UTCEG score recompute
- 2026-07-11 20:35 UTCVendor advisory
- 2026-07-11 16:20 UTCEG score recompute
- 2026-07-11 16:20 UTCVendor advisory
- 2026-07-11 12:05 UTCEG score recompute
- 2026-07-11 12:05 UTCVendor advisory
- 2026-07-11 07:51 UTCEG score recompute
- 2026-07-11 07:51 UTCVendor advisory
- 2026-07-11 03:36 UTCEG score recompute
- 2026-07-11 03:36 UTCVendor advisory
- 2026-07-10 23:21 UTCEG score recompute
- 2026-07-10 23:21 UTCVendor advisory
- 2026-07-10 19:07 UTCEG score recompute
- 2026-07-10 19:07 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
Show 75 moreShow fewer
- 2026-07-10 14:52 UTCEG score recompute
- 2026-07-10 14:52 UTCVendor advisory
- 2026-07-10 10:37 UTCEG score recompute
- 2026-07-10 10:37 UTCVendor advisory
- 2026-07-10 06:19 UTCEG score recompute
- 2026-07-10 06:19 UTCVendor advisory
- 2026-07-10 02:04 UTCEG score recompute
- 2026-07-10 02:04 UTCVendor advisory
- 2026-07-09 21:47 UTCEG score recompute
- 2026-07-09 21:47 UTCVendor advisory
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-09 17:33 UTCEG score recompute
- 2026-07-09 17:33 UTCVendor advisory
- 2026-07-09 13:19 UTCEG score recompute
- 2026-07-09 13:19 UTCVendor advisory
- 2026-07-09 09:04 UTCEG score recompute
- 2026-07-09 09:04 UTCVendor advisory
- 2026-07-09 04:48 UTCEG score recompute
- 2026-07-09 04:48 UTCVendor advisory
- 2026-07-09 00:33 UTCEG score recompute
- 2026-07-09 00:33 UTCVendor advisory
- 2026-07-08 20:18 UTCEG score recompute
- 2026-07-08 20:18 UTCVendor advisory
- 2026-07-08 16:04 UTCEG score recompute
- 2026-07-08 16:04 UTCVendor advisory
- 2026-07-08 11:48 UTCEG score recompute
- 2026-07-08 11:48 UTCVendor advisory
- 2026-07-08 07:31 UTCEG score recompute
- 2026-07-08 07:31 UTCVendor advisory
- 2026-07-08 03:16 UTCEG score recompute
- 2026-07-08 03:16 UTCVendor advisory
- 2026-07-07 23:00 UTCEG score recompute
- 2026-07-07 23:00 UTCVendor advisory
- 2026-07-07 19:01 UTCCISA KEV update
- 2026-07-07 18:46 UTCEG score recompute
- 2026-07-07 18:46 UTCVendor advisory
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 14:29 UTCEG score recompute
- 2026-07-07 14:29 UTCVendor advisory
- 2026-07-07 10:12 UTCEG score recompute
- 2026-07-07 10:12 UTCVendor advisory
- 2026-07-07 05:55 UTCEG score recompute
- 2026-07-07 05:55 UTCVendor advisory
- 2026-07-07 01:41 UTCEG score recompute
- 2026-07-07 01:41 UTCVendor advisory
- 2026-07-06 21:27 UTCEG score recompute
- 2026-07-06 21:27 UTCVendor advisory
- 2026-07-06 17:10 UTCEG score recompute
- 2026-07-06 17:10 UTCVendor advisory
- 2026-07-06 12:56 UTCEG score recompute
- 2026-07-06 12:56 UTCVendor advisory
- 2026-07-06 08:40 UTCEG score recompute
- 2026-07-06 08:40 UTCVendor advisory
- 2026-07-06 04:25 UTCEG score recompute
- 2026-07-06 04:25 UTCVendor advisory
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-06 00:10 UTCEG score recompute
- 2026-07-06 00:10 UTCVendor advisory
- 2026-07-05 19:55 UTCEG score recompute
- 2026-07-05 19:55 UTCVendor advisory
- 2026-07-05 15:40 UTCEG score recompute
- 2026-07-05 15:40 UTCVendor advisory
- 2026-07-05 11:25 UTCEG score recompute
- 2026-07-05 11:25 UTCVendor advisory
- 2026-07-05 07:10 UTCEG score recompute
- 2026-07-05 07:10 UTCVendor advisory
- 2026-07-05 02:54 UTCEG score recompute
- 2026-07-05 02:54 UTCVendor advisory
- 2026-07-04 22:40 UTCEG score recompute
- 2026-07-04 22:40 UTCVendor advisory
- 2026-07-04 18:25 UTCEG score recompute
- 2026-07-04 18:25 UTCVendor advisory
- 2026-07-04 14:10 UTCEG score recompute
- 2026-07-04 14:10 UTCVendor advisory
- 2026-07-04 09:55 UTCEG score recompute
Publicly available exploits
(3 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCVenscor/CVE-2018-14667-pocFirst seen Sep 23, 2019
CVE-2018-14667-poc Richfaces漏洞环境及PoC
Open source ↗ - GitHub PoCsyriusbughunt/CVE-2018-14667First seen Nov 30, 2018
All about CVE-2018-14667; From what it is to how to successfully exploit it.
Open source ↗ - Open source ↗GitHub PoCzeroto01/CVE-2018-14667First seen Nov 23, 2018
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(6)
What is CVE-2018-14667?
When was CVE-2018-14667 disclosed?
Is CVE-2018-14667 actively exploited?
What is the CVSS score of CVE-2018-14667?
Which products are affected by CVE-2018-14667?
How do I remediate CVE-2018-14667?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-14667
Is Your Infrastructure Affected by CVE-2018-14667?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.