CVE-2018-12415 json
TIBCO Enterprise Message Service Vulnerable to CSRF Attacks
published 2018-11-06 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-4389
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
The Central Administration server (emsca) component of TIBCO Software Inc.'s TIBCO Enterprise Message Service, TIBCO Enterprise Message Service - Community Edition, and TIBCO Enterprise Message Service - Developer Edition contains a vulnerability which may allow an attacker to perform cross-site request forgery (CSRF) attacks. Affected releases are TIBCO Software Inc.'s TIBCO Enterprise Message Service: versions 8.4.0 and below, TIBCO Enterprise Message Service - Community Edition: versions 8.4.0 and below, and TIBCO Enterprise Message Service - Developer Edition: versions 8.4.0 and below.
Exploit prediction
0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- TIBCO Software Inc. TIBCO Enterprise Message Service
- TIBCO Software Inc. TIBCO Enterprise Message Service - Community Edition
- TIBCO Software Inc. TIBCO Enterprise Message Service - Developer Edition
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
tibco.com
/services/support/advisories
vendor-advisory
-
tibco.com
/support/advisories/2018/11/tibco-security-advisory-november-6-2018-tibco-enterprise-messaging-service
vendor-advisory
-
securityfocus.com
/bid/105850
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-12415
- NVD CVE-2018-12415
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.