Live Vulnerability Intelligence
Threat Database
Search CVEs, inspect descriptions, and open detail pages with AI-assisted technical context.
Threat Entry
Updated 2025-05-12
CVE-2025-2816 - Page View Count Plugin
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…
PLUGIN
Page View Count
CVE-2025-2816
Risk Score
Threat Entry
Updated 2025-03-25
CVE-2023-0095 - Page View Count Plugin
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.
PLUGIN
Page View Count
CVE-2023-0095
Risk Score
Threat Entry
Updated 2024-11-21
CVE-2022-40131 - Page View Count Plugin
Cross-Site Request Forgery (CSRF) vulnerability in a3rev Software Page View Count plugin
PLUGIN
Page View Count
CVE-2022-40131
Risk Score
Threat Entry
Updated 2024-11-21
CVE-2022-0434 - Page View Count Plugin
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
PLUGIN
Page View Count
CVE-2022-0434
Risk Score
Threat Entry
Updated 2024-11-21
CVE-2021-24509 - Page View Count Plugin
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.
PLUGIN
Page View Count
CVE-2021-24509
Risk Score