Page View Count 2.8.0 - 2.8.4 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update
Strategic Overview
- Status
- Patched in 2.8.5
- Affected Plugin
- Page View Count
- Affected Version
2.8.0 – 2.8.4- CVSS
- 8.1High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-2816
At a glance
CVE-2025-2816 is a high-severity Missing Authorization vulnerability in the Page View Count WordPress plugin, affecting versions 2.8.0 – 2.8.4. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.8.5; sites on affected versions should update now. Disclosed April 2025, reported by kr0d.
Vulnerability Overview
The Page View Count plugin for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to a missing capability check on the yellow_message_dontshow() function in versions 2.8.0 to 2.8.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update option values to one on the WordPress site. This can be leveraged to update an option that would create an error on the site and deny service to legitimate users or be used to set some values to true such as registration.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-862: Missing Authorization
Page View Count 2.8.0 – 2.8.4 carries this weakness at yellow_message_dontshow(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Page View Count the fix is 2.8.5: builds 2.8.0 – 2.8.4 are affected, anything from 2.8.5 onward is not.
Remediation
Update to version 2.8.5, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Page View Count 2.8.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Page View Count
- 9.8CVE-2022-0434: Page Views Count Plugin <= 2.4.14 SQL Injection
CVE-2022-0434 - 8.8CVE-2022-40131: Page View Count <= 2.5.5 Cross-Site Request Forgery
CVE-2022-40131 - 6.4CVE-2023-0095: Page View Count <= 2.6.0 Stored Cross-Site Scripting
CVE-2023-0095 - 5.4CVE-2021-24509: Page View Counts <= 2.4.8 Contributor+ Stored XSS
CVE-2021-24509
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C