HomeWordPress vulnerabilitiesiubenda
iubenda vulnerabilities
iubenda has 4 known vulnerabilities in this database. The most recent published record is dated 5 Sep 2026.
- Known vulnerabilities
- 4
- Active installs
- 200,000+
- Latest version
- 3.13.5
- Last updated
- 1 Sep 2026
- Most recent
- 5 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-77233 | High 7.2 | Up to 3.13.4 | Fixed in a later version (latest 3.13.5) | 5 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-77263 | High 7.2 | Up to 3.13.4 | Fixed in a later version (latest 3.13.5) | 5 Sep 2026 |
| Cross-site request forgery (CSRF) CVE-2022-3911 | High 8.8 | Before 3.3.3 | Fixed in 3.3.3 | 2 Jan 2023 |
| Security weakness CVE-2020-12742 | Medium 6.1 | Before 2.3.5 | Fixed in 2.3.5 | 13 May 2020 |
Read the published descriptions
- CVE-2026-77233, 5 Sep 2026
- The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via AdSense Regex Rewrite in all versions up to, and including, 3.13.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability only manifests when the 'Secondary' parser engine is active (parser_engine=default); it does not exist under the default 'new' DOM-based parser engine. CVE record
- CVE-2026-77263, 5 Sep 2026
- The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 3.13.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit works by embedding KSES-allowed markup such as abbr title attributes and HTML comments in a submitted comment so that the global strtr() substitution strips substrings from an inert tag, mutating it into an executable element such as an img onerror handler that runs in the WordPress origin for any visitor, including logged-in administrators. CVE record
- CVE-2022-3911, 2 Jan 2023
- The iubenda WordPress plugin before 3.3.3 does does not have authorisation and CSRF in an AJAX action, and does not ensure that the options to be updated belong to the plugin as long as they are arrays. As a result, any authenticated users, such as subscriber can grant themselves any privileges, such as edit_plugins etc CVE record
- CVE-2020-12742, 13 May 2020
- The iubenda-cookie-law-solution plugin before 2.3.5 for WordPress does not restrict URL sanitization to http protocols. CVE record
What to do if you run iubenda
If you run iubenda, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new iubenda vulnerabilities
Free. We email you when a new vulnerability is published for iubenda, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.