The Inline frame – Iframe plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'embedsite'
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium.
Data as of 18 Nov 2026, 02:30 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
AI-suggested
Users should restrict contributor-level access to trusted individuals and consider disabling or removing the Inline frame – Iframe plugin until a fix is available. Monitor the vendor's advisory channels for updates regarding remediation.
Description
The Inline frame – Iframe plugin for WordPress versions up to and including 0.1 contains a stored cross-site scripting (XSS) vulnerability via the 'embedsite' shortcode. This vulnerability arises from insufficient input sanitization and output escaping of user-supplied attributes, allowing authenticated users with contributor-level access or higher to inject arbitrary scripts. These scripts execute whenever a user accesses the affected page, potentially compromising user data and session integrity.