Live › vulnerability › CVE-2026-96741
The DSGVO All in one for WP WordPress plugin, up to and including version 5.0, does not sanitize comment content before writing it into pages. An unauthenticated attacker can plant a script in a comment that runs in the browser of anyone who opens the affected page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 04:41 UTC. All times on this page are UTC.
Only WordPress sites running the DSGVO All in one for WP plugin at version 5.0 or lower, with both the Google Tag Manager integration and the automatic replacement beta option enabled. The attack also needs an administrator to approve the crafted comment before it is stored on a page. Sites without those settings enabled, or without the plugin, are not affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| dsgvo-all-in-one-for-wp | wordpress-plugin | <= 5.0 | – |
5.0 or lowerReplace integration automatically [Beta] option and do not approve untrusted commentsEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The DSGVO All in one for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Output Buffer Regex Corruption in all versions up to, and including, 5.0 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 is only exploitable when the administrator has enabled both the 'Google Tag Manager' integration and the 'Replace integration automatically [Beta]' option, and requires the crafted comment to be approved by an administrator.
This page as .md · .json · in your agent: get_signal("CVE-2026-96741")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.