CVE-2025-26961: WordPress Fresh Framework plugin <= 1.70.0 - Unauthenticated Broken Access Control vulnerability
First published: Sat Mar 15 2025(Updated: )
Missing Authorization vulnerability in NotFound Fresh Framework allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Fresh Framework: from n/a through 1.70.0.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Fresh Framework | <=1.70.0 | |
| WordPress Fresh Framework | <=1.70.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-26961?
CVE-2025-26961 is classified as a high severity missing authorization vulnerability.
How do I fix CVE-2025-26961?
To fix CVE-2025-26961, you should update the Fresh Framework to version 1.70.1 or higher.
What types of systems are affected by CVE-2025-26961?
CVE-2025-26961 affects Fresh Framework and the WordPress Fresh Framework plugin up to version 1.70.0.
What impact does CVE-2025-26961 have on system security?
CVE-2025-26961 allows unauthorized access to functionality not properly constrained by access control lists (ACLs).
Is CVE-2025-26961 under active exploit?
As of the latest information, there are no confirmed reports of active exploitation for CVE-2025-26961.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- agent/author
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/fresh framework
- canonical/fresh framework
- vendor/wordpress
- canonical/wordpress fresh framework