CVE-2023-6684: Ibtana (WordPress plugin) · Cross-site Scripting
Affects Ibtana (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 11 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vowelweb Ibtana – WordPress Website Builder | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their WordPress installations to identify the presence of the Ibtana – WordPress Website Builder plugin and verify the version in use. Until an official patch is released, organizations should consider the following specific mitigations: 1) Restrict contributor-level permissions strictly to trusted users and review user roles regularly to minimize the risk of insider exploitation. 2) Implement Web Application Firewall (WAF) rules that detect and block suspicious input patterns targeting the 'ive' shortcode attributes, particularly filtering out script tags or event handlers in 'width' and 'height' parameters. 3) Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected websites. 4) Conduct thorough input validation and output encoding on custom implementations or overrides related to the plugin to prevent injection. 5) Monitor website logs and user activity for unusual behavior indicative of exploitation attempts. 6) Engage with the plugin vendor or community to track patch releases and apply updates promptly once available. 7) Consider temporarily disabling or removing the plugin if feasible, especially on high-risk or critical sites, until the vulnerability is resolved.
Description
The Ibtana – WordPress Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ive' shortcode in versions up to, and including, 1.2.2 due to insufficient input sanitization and output escaping on 'width' and 'height' user supplied attribute. This makes it possible for authenticated attackers with contributor level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
References
- wordfence.com/threat-intel/vulnerabilities/id/0b09d496-0e03-48a4-acf7-57febe18ed0a?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/ibtana-visual-editor/trunk/ive-countdown.php?rev=2965648 (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3006647/ibtana-visual-editor/trunk/ive-countdown.php (opens in a new tab)