# CVE-2025-26773: WordPress Analytify plugin <= 5.5.0 - Broken Access Control vulnerability

> Attackers can bypass access controls in the Analytify WordPress plugin to perform unauthorized actions due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-v2jq-794f-f847

## What is CVE-2025-26773?

CVE-2025-26773 is a medium-severity missing authorization vulnerability in Adnan Analytify, published on 17 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Adnan Analytify wp-analytify allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Analytify: from n/a through <= 5.5.0.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-26773?

It affects 1 product.


Products: Analytify Analytify - Google Analytics Dashboard.

## How do I fix CVE-2025-26773?

No fix has been published for CVE-2025-26773 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-26773 being exploited?

There is no known exploitation of CVE-2025-26773 in the wild and no public exploit code.

## Other vulnerabilities in Adnan Analytify

- [CVE-2022-45830](https://insights.sbomify.com/CVE-2022-45830/): WordPress Analytify - Google Analytics Dashboard plugin <= 4.2.3 - Privilege Escalation vulnerability (medium 6.5)
- [CVE-2024-53814](https://insights.sbomify.com/CVE-2024-53814/): WordPress Analytify plugin <= 5.4.3 - Broken Access Control vulnerability (medium 6.5)
- [CVE-2024-35689](https://insights.sbomify.com/CVE-2024-35689/): WordPress Analytify plugin <= 5.2.3 - Cross Site Request Forgery (CSRF) vulnerability (medium 5.4)
- [CVE-2024-1809](https://insights.sbomify.com/CVE-2024-1809/): Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) <= 5.2.3 - Missing Authorization (medium 5.4)
- [CVE-2024-1584](https://insights.sbomify.com/CVE-2024-1584/): Analytify <= 5.2.1 - Missing Authorization to Unauthenticated Google Analytics Tracking ID Modification (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26773 and fix it if it is affected.

What it is: CVE-2025-26773 is a medium-severity missing authorization vulnerability in Adnan Analytify, published on 17 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26773 in the wild and no public exploit code.

Affected product: Adnan Analytify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-26773/ (Markdown: https://insights.sbomify.com/CVE-2025-26773/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26773
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26773
- OSV: https://osv.dev/vulnerability/CVE-2025-26773

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-26773/
Summaries are generated and may contain mistakes; the official description above is the record.