HomeWordPress vulnerabilitiesPage View Count
Page View Count vulnerabilities
Page View Count has 5 known vulnerabilities in this database. The most recent published record is dated 1 May 2025.
- Known vulnerabilities
- 5
- Active installs
- 10,000+
- Latest version
- 2.9.2
- Last updated
- 9 Jul 2026
- Most recent
- 1 May 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2025-2816 | High 8.1 | Before 2.8.5 | Fixed in 2.8.5 | 1 May 2025 |
| Cross-site scripting (XSS) CVE-2023-0095 | Medium 5.4 | Before 2.6.1 | Fixed in 2.6.1 | 6 Feb 2023 |
| Cross-site request forgery (CSRF) CVE-2022-40131 | Medium 5.4 | Up to 2.5.5 | Fixed in a later version (latest 2.9.2) | 3 Nov 2022 |
| SQL injection CVE-2022-0434 | Critical 9.8 | Before 2.4.15 | Fixed in 2.4.15 | 7 Mar 2022 |
| Cross-site scripting (XSS) CVE-2021-24509 | Medium 5.4 | Before 2.4.9 | Fixed in 2.4.9 | 9 Aug 2021 |
Read the published descriptions
- CVE-2025-2816, 1 May 2025
- 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. CVE record
- CVE-2023-0095, 6 Feb 2023
- The Page View Count WordPress plugin before 2.6.1 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. CVE record
- CVE-2022-40131, 3 Nov 2022
- Cross-Site Request Forgery (CSRF) vulnerability in a3rev Software Page View Count plugin <= 2.5.5 on WordPress allows an attacker to reset the plugin settings. CVE record
- CVE-2022-0434, 7 Mar 2022
- The Page View Count WordPress plugin before 2.4.15 does not sanitise and escape the post_ids parameter before using it in a SQL statement via a REST endpoint, available to both unauthenticated and authenticated users. As a result, unauthenticated attackers could perform SQL injection attacks CVE record
- CVE-2021-24509, 9 Aug 2021
- The Page View Count WordPress plugin before 2.4.9 does not escape the postid parameter of pvc_stats shortcode, allowing users with a role as low as Contributor to perform Stored XSS attacks. A post made by a contributor would still have to be approved by an admin to have the XSS triggered in the frontend, however, higher privilege users, such as editor could exploit this without the need of approval, and even when the blog disallows the unfiltered_html capability. CVE record
What to do if you run Page View Count
If you run Page View Count, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Page View Count vulnerabilities
Free. We email you when a new vulnerability is published for Page View Count, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.