CVE-2015-10094 json
Fastly Plugin api.php post cross site scripting
published 3y ago modified 4mo ago also EUVD-2015-1104
- cvss
- 2.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
A vulnerability was found in Fastly Plugin up to 0.97 on WordPress. It has been rated as problematic. Affected by this issue is the function post of the file lib/api.php. The manipulation of the argument url leads to cross site scripting. The attack may be launched remotely. Upgrading to version 0.98 is able to address this issue. The patch is identified as d7fe42538f4d4af500e3af9678b6b06fba731656. It is recommended to upgrade the affected component. VDB-222326 is the identifier assigned to this vulnerability.
Patch / fix
- fastly fastly 0.98
Is CVE-2015-10094 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.4 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N |
| CNA | 3.0 | 2.4 | CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N |
| CNA | 2.0 | 3.3 | AV:N/AC:L/Au:M/C:N/I:P/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- n/a Fastly Plugin
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
github.com
/wp-plugins/fastly/commit/d7fe42538f4d4af500e3af9678b6b06fba731656
patch
-
github.com
/wp-plugins/fastly/releases/tag/0.98
patch, release-notes
-
vuldb.com
/?id.222326
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.222326
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2015-10094
- NVD CVE-2015-10094
Fencer Intel 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.