CVE-2026-22517

Unknown Unknown - Not Provided

Missing Authorization in GA4WP Plugin Enables Unauthorized Access

Publication date: 2026-01-08

Last updated on: 2026-04-23

Assigner: Patchstack

Description

Missing Authorization vulnerability in Passionate Brains GA4WP: Google Analytics for WordPress ga-for-wp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GA4WP: Google Analytics for WordPress: from n/a through <= 2.10.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-01-08

Last Modified

2026-04-23

Generated

2026-07-06

AI Q&A

2026-01-08

EPSS Evaluated

2026-07-05

NVD

CVE-2026-22517

EUVD

EUVD-2026-1484

Affected Vendors & Products

Vendor	Product	Version / Range
passionate_brains	ga4wp	From 2.10.0\|end_including=2.10.0 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability is a Broken Access Control issue in the GA4WP: Google Analytics for WordPress plugin (up to version 2.10.0). It occurs because of missing authorization, authentication, or nonce token checks in certain functions, which allows users with low privileges (Subscriber-level) to perform actions that should be restricted to higher-privileged roles like Developer. [1]

Impact Analysis

The vulnerability allows unprivileged users to perform actions reserved for higher-privileged roles, potentially leading to unauthorized changes or actions within the plugin. However, the CVSS score of 5.4 indicates a low severity and low impact threat, and exploitation is considered unlikely. [1]

Mitigation Strategies

Since no official fix or patched version is currently available for this vulnerability, immediate mitigation steps include using Patchstack's mitigation and security intelligence services to help protect affected sites. Additionally, reviewing user roles and permissions to ensure that Subscriber-level users do not have unintended access to higher-privileged functions may reduce risk. [1]

Hi! I’m here to help you understand CVE-2026-22517. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70