Skip to content
vulneraibility.com
Screener

CVE-2018-14667

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.

CVSS
9.8Criticalscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 28 Sept 2023CISA deadline for US federal agencies: 19 Oct 2023unvetted proof-of-concept code on github
EPSS
74.2%chance of exploitation in the next 30 daystop 0.6% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
6 Nov 2018analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
[UNKNOWN] RichFacesaffected 3.X through 3.3.4Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • redhat:richfaces
  • redhat:enterprise_linux

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.

Also consider: remove eval sinks · RASP

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 28 Sept 2023.
CISA due date
19 Oct 2023, the remediation deadline for US federal agencies
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code
Unvetted proof-of-concept code on GitHub: 7 GitHub proofs of concept
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 7 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

and 3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 6 Nov 2018Published
  2. 18 Nov 2018First proof-of-concept repository on GitHub (unvetted)11 days later
  3. 28 Sept 2023Added to CISA KEV (exploited in the wild)1,775 days (about 5 years) later
  4. 19 Oct 2023CISA remediation due date (US federal agencies)21 days later
  5. 7 Feb 2025CISA SSVC assessment: exploitation active478 days (about 1 year) later
  6. 21 Oct 2025CVE record last updated256 days (about 9 months) later
  7. 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2018-14667 being exploited?

Yes. CVE-2018-14667 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2018-14667?

CVE-2018-14667 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2018-14667?

Yes. A fix has been recorded for CVE-2018-14667. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2018-14667 affect?

CVE-2018-14667 affects redhat:richfaces, redhat:enterprise_linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

9 references in the CVE record, grouped by the tags the record gives them.

Advisories (4)

Other links (5)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com