JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for JBoss Expression Language (EL) expressions, which allows remote attackers to execute arbitrary code via a crafted URL. NOTE: this is only a vulnerability when the Java Security Manager is not properly configured.
CVE-2010-1871
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-12-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 83%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
August 5, 2010
Last Modified
April 22, 2026
Advisory Details (6)
Auto-updated May 2, 2026615956 – (CVE-2010-1871) CVE-2010-1871 JBoss Seam / Seam2: Improper sanitization of parametrized JBoss EL expressions (ACE)
https://bugzilla.redhat.com/show_bug.cgi?id=615956VUPEN Security - Vulnerability Research and Intelligence
http://www.vupen.com/english/advisories/2010/1929Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | jboss-seam2-0:2.0.2.FP-1.ep1.24.el5 | 2010-07-27 | 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.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
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 61× in last 7d / 332× 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 684 total refreshes for this CVE.
- 2026-07-27 05:08 UTCVendor advisory
- 2026-07-27 05:08 UTCGHSA enrichment
- 2026-07-27 00:45 UTCVendor advisory
- 2026-07-27 00:45 UTCGHSA enrichment
- 2026-07-26 20:22 UTCVendor advisory
- 2026-07-26 20:22 UTCGHSA enrichment
- 2026-07-26 15:57 UTCEG score recompute
- 2026-07-26 15:57 UTCVendor advisory
- 2026-07-26 15:57 UTCGHSA enrichment
- 2026-07-26 11:34 UTCEG score recompute
- 2026-07-26 11:34 UTCVendor advisory
- 2026-07-26 11:33 UTCGHSA enrichment
- 2026-07-26 07:08 UTCVendor advisory
- 2026-07-26 07:08 UTCGHSA enrichment
- 2026-07-26 02:44 UTCEG score recompute
- 2026-07-26 02:44 UTCVendor advisory
- 2026-07-26 02:44 UTCGHSA enrichment
- 2026-07-23 14:14 UTCEPSS rescore
- 2026-07-23 01:01 UTCEG score recompute
- 2026-07-23 00:38 UTCEG score recompute
- 2026-07-22 23:41 UTCEG score recompute
- 2026-07-22 23:41 UTCVendor advisory
- 2026-07-22 23:40 UTCGHSA enrichment
- 2026-07-22 21:45 UTCEG score recompute
- 2026-07-22 19:40 UTCCISA KEV update
Show 75 moreShow fewer
- 2026-07-22 19:18 UTCVendor advisory
- 2026-07-22 19:17 UTCGHSA enrichment
- 2026-07-22 14:53 UTCEG score recompute
- 2026-07-22 14:53 UTCVendor advisory
- 2026-07-22 14:53 UTCGHSA enrichment
- 2026-07-22 14:03 UTCEPSS rescore
- 2026-07-22 14:03 UTCEPSS rescore
- 2026-07-22 10:25 UTCVendor advisory
- 2026-07-22 10:25 UTCGHSA enrichment
- 2026-07-22 06:02 UTCVendor advisory
- 2026-07-22 06:02 UTCGHSA enrichment
- 2026-07-22 01:37 UTCVendor advisory
- 2026-07-22 01:37 UTCGHSA enrichment
- 2026-07-21 21:02 UTCVendor advisory
- 2026-07-21 21:02 UTCGHSA enrichment
- 2026-07-21 16:39 UTCEG score recompute
- 2026-07-21 16:39 UTCVendor advisory
- 2026-07-21 16:39 UTCGHSA enrichment
- 2026-07-21 15:20 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:16 UTCVendor advisory
- 2026-07-21 12:16 UTCGHSA enrichment
- 2026-07-21 07:52 UTCVendor advisory
- 2026-07-21 07:52 UTCGHSA enrichment
- 2026-07-21 03:28 UTCVendor advisory
- 2026-07-21 03:28 UTCGHSA enrichment
- 2026-07-20 23:05 UTCVendor advisory
- 2026-07-20 23:05 UTCGHSA enrichment
- 2026-07-20 18:42 UTCEG score recompute
- 2026-07-20 18:42 UTCVendor advisory
- 2026-07-20 18:42 UTCGHSA enrichment
- 2026-07-20 17:03 UTCEPSS rescore
- 2026-07-20 14:19 UTCVendor advisory
- 2026-07-20 14:19 UTCGHSA enrichment
- 2026-07-20 09:56 UTCVendor advisory
- 2026-07-20 09:56 UTCGHSA enrichment
- 2026-07-20 05:34 UTCVendor advisory
- 2026-07-20 05:34 UTCGHSA enrichment
- 2026-07-20 01:10 UTCVendor advisory
- 2026-07-19 20:47 UTCVendor advisory
- 2026-07-19 20:47 UTCGHSA enrichment
- 2026-07-19 16:24 UTCVendor advisory
- 2026-07-19 16:24 UTCGHSA enrichment
- 2026-07-19 12:01 UTCVendor advisory
- 2026-07-19 12:01 UTCGHSA enrichment
- 2026-07-19 07:39 UTCVendor advisory
- 2026-07-19 07:39 UTCGHSA enrichment
- 2026-07-19 03:16 UTCVendor advisory
- 2026-07-19 03:16 UTCGHSA enrichment
- 2026-07-18 22:53 UTCVendor advisory
- 2026-07-18 22:53 UTCGHSA enrichment
- 2026-07-18 18:30 UTCVendor advisory
- 2026-07-18 18:30 UTCGHSA enrichment
- 2026-07-18 14:07 UTCVendor advisory
- 2026-07-18 14:07 UTCGHSA enrichment
- 2026-07-18 09:44 UTCVendor advisory
- 2026-07-18 09:44 UTCGHSA enrichment
- 2026-07-18 05:21 UTCVendor advisory
- 2026-07-18 05:21 UTCGHSA enrichment
- 2026-07-18 00:58 UTCVendor advisory
- 2026-07-18 00:58 UTCGHSA enrichment
- 2026-07-17 20:35 UTCVendor advisory
- 2026-07-17 20:35 UTCGHSA enrichment
- 2026-07-17 16:12 UTCVendor advisory
- 2026-07-17 16:11 UTCGHSA enrichment
- 2026-07-17 11:48 UTCVendor advisory
- 2026-07-17 11:48 UTCGHSA enrichment
- 2026-07-17 07:25 UTCEG score recompute
- 2026-07-17 07:25 UTCVendor advisory
- 2026-07-17 07:25 UTCGHSA enrichment
- 2026-07-17 03:02 UTCVendor advisory
- 2026-07-17 03:02 UTCGHSA enrichment
- 2026-07-16 22:39 UTCVendor advisory
- 2026-07-16 22:39 UTCGHSA enrichment
- 2026-07-16 18:16 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (2 Metasploit modules) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-36653✓ verifiedFirst seen Apr 6, 2015
JBoss Seam 2 - Arbitrary File Upload / Execution (Metasploit)
Open source ↗ - Metasploitexploit/multi/http/jboss_seam_upload_exec✓ verifiedFirst seen Aug 5, 2010
JBoss Seam 2 File Upload and Execute
Open source ↗ - Metasploitauxiliary/admin/http/jboss_seam_exec✓ verifiedFirst seen Jul 19, 2010
JBoss Seam 2 Remote Command Execution
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p90HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p92HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(6)
What is CVE-2010-1871?
When was CVE-2010-1871 disclosed?
Is CVE-2010-1871 actively exploited?
What is the CVSS score of CVE-2010-1871?
Which products are affected by CVE-2010-1871?
How do I remediate CVE-2010-1871?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2010-1871
Is Your Infrastructure Affected by CVE-2010-1871?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.