CVE-2025-8089 json
Advanced iFrame <= 2025.6 - Authenticated (Contributor+) Stored Cross-Site Scripting
published last yr. modified 4mo ago also EUVD-2025-25074
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
The Advanced iFrame plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'additional' parameter in version less than, or equal to, 2025.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Patch / fix
- tinywebgallery advanced_iframe 2025.7
Is CVE-2025-8089 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- mdempfle Advanced iFrame
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/97985b75-6ac9-4aba-8f76-5633418e7907?source=cve
- plugins.trac.wordpress.org /browser/advanced-iframe/trunk/advanced-iframe.php#L1831
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3344404%40advanced-iframe&new=3344404%40advanced-iframe&sfp_ema
Sources
- CVE List CVE-2025-8089
- NVD CVE-2025-8089
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.