---
title: "CVE-2026-88904: PuppyFW WordPress plugin - Broken Access Control"
description: "PuppyFW WordPress plugin through 0.4.4 contains a broken access control caused by improper authorization on a REST route, letting any authenticated user escalate privileges by modifying blog options."
url: https://panop.io/threat-heartbeat/CVE-2026-88904/
---

# CVE-2026-88904 PuppyFW WordPress plugin - Broken Access Control

PuppyFW WordPress plugin through 0.4.4 contains a broken access control caused by improper authorization on a REST route, letting any authenticated user escalate privileges by modifying blog options.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.42% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-88904)

## Details

Type

Broken Access Control

Impact

Privilege Escalation

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

17 September 2026

Updated

15 October 2026

Weakness

[CWE-269](https://cwe.mitre.org/data/definitions/269.html)

## Vendor fix

Update to the latest version of PuppyFW WordPress plugin.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-88904](https://nvd.nist.gov/vuln/detail/CVE-2026-88904)
- [https://wpscan.com/vulnerability/d65eff64-0c20-4cfe-8ba2-1d202a5e4306/](https://wpscan.com/vulnerability/d65eff64-0c20-4cfe-8ba2-1d202a5e4306/)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)