Patchstack published a GTM Server Side vulnerability notice on November 4, 2026: versions earlier than 2.3.11 are affected by an unauthenticated server-side request forgery (SSRF) flaw rated CVSS 7.1. The fix is available in version 2.3.11.
If you use the plugin, check its installed version and update to 2.3.11 or later. Patchstack classifies the issue as medium priority and says the required privilege is unauthenticated. The notice does not say the vulnerability is being actively exploited.
What the GTM Server Side vulnerability affects
The affected software is GTM Server Side, a WordPress plugin. Patchstack lists every version below 2.3.11 as vulnerable and version 2.3.11 as patched. Its record identifies the issue as SSRF and gives it a CVSS severity score of 7.1.
“Unauthenticated” is the detail site owners should not overlook: Patchstack lists no required user privilege for exploitation. That describes the access level required, not evidence that attacks are underway. The entry offers no report of active exploitation, affected-site counts, or technical details about how the flaw works.
Those limits matter. The published information supports a clear update recommendation, but it does not establish how widely the vulnerable versions are installed or whether a particular site has been targeted. Avoid treating the CVSS score alone as proof of an ongoing incident.
How to respond to the GTM Server Side vulnerability
First, find out whether GTM Server Side is installed and check its version. If it is earlier than 2.3.11, update it to version 2.3.11 or later, the release Patchstack identifies as resolving the issue.
If the plugin is not installed, no plugin update is needed for this specific vulnerability. If an update cannot be applied immediately, Patchstack says it has issued a mitigation rule to block attacks until a patched version is installed. Its notice does not provide further details about that rule, so do not assume a mitigation is active on your site unless your security setup confirms it.
After updating, confirm the installed version in your site’s plugin list. Keep the check focused: the affected plugin, the version boundary, and the available fix are the concrete details in Patchstack’s notice.
What the notice does and does not establish
Patchstack published the record on November 4, 2026, and credits Joep van Antwerpen. It assigns medium priority, reports CVSS 7.1, and lists the issue as unauthenticated. Those are the facts site owners can use to prioritize an update.
The notice does not report active exploitation, describe attacker behavior, or quantify the number of affected sites. It also does not provide a detailed technical explanation of the flaw on the page. For that reason, this is a timely patch advisory, not a claim that GTM Server Side users are facing a confirmed campaign.
The practical takeaway is straightforward: check for the plugin, verify whether the installed version is earlier than 2.3.11, then update if needed. Where a site cannot update at once, verify whether the mitigation Patchstack describes is available in its security setup.
FAQ
Which GTM Server Side versions are vulnerable?
Patchstack lists versions earlier than 2.3.11 as vulnerable. It lists version 2.3.11 as patched.
Does this vulnerability require a logged-in WordPress account?
No. Patchstack lists the required privilege as unauthenticated. The notice does not say that the vulnerability is being actively exploited.
What should site owners do?
Check whether GTM Server Side is installed and update any version earlier than 2.3.11 to version 2.3.11 or later. If you cannot update immediately, confirm whether the mitigation Patchstack describes is active for your site.
Next step: Check your WordPress plugin list today and update GTM Server Side if it is below version 2.3.11.