Page View Count at a glance
- 6 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Dec 8, 2025.
- Ranked #1527 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 2.9.2 (released Jul 9, 2026). The most recent security fix shipped in 2.9.2.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Page View Count version
Enter the Page View Count version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Page View Count”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Page View Count”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.9.2). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Page View Count vulnerabilities
Page View Count <= 2.9.1 - Missing Authorization to Authenticated (Subscriber+) Settings Update
Missing authorization · CVE-2025-63034
Affected versions: ≤ 2.9.1
Fixed in: 2.9.2
Severity: Medium 4.3 · Disclosed Dec 8, 2025
Page View Count 2.8.0 - 2.8.4 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update
Missing authorization · CVE-2025-2816
Affected versions: ≥ 2.8.0, ≤ 2.8.4
Fixed in: 2.8.5
Severity: High 8.1 · Disclosed Apr 30, 2025
Page View Count <= 2.6.0 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-0095
Affected versions: ≤ 2.6.0
Fixed in: 2.6.1
Severity: Medium 6.4 · Disclosed Jan 10, 2023
Page View Count <= 2.5.5 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2022-40131
Affected versions: ≤ 2.5.5
Fixed in: 2.5.6
Severity: High 8.8 · Disclosed Oct 13, 2022
Page Views Count Plugin <= 2.4.14 - Unauthenticated SQL Injection
SQL injection · CVE-2022-0434
Affected versions: < 2.4.15
Fixed in: 2.4.15
Severity: Critical 9.8 · Disclosed Feb 1, 2022
Page View Counts <= 2.4.8 - Contributor+ Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-24509
Affected versions: ≤ 2.4.8
Fixed in: 2.4.9
Severity: Medium 5.4 · Disclosed Jul 12, 2021
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Page View Count <= 2.9.1 - Missing Authorization to Authenticated (Subscriber+) Settings UpdateMissing authorization · CVE-2025-63034 | ≤ 2.9.1 | 2.9.2 | Medium 4.3 | Dec 8, 2025 |
| Page View Count 2.8.0 - 2.8.4 - Missing Authorization to Authenticated (Subscriber+) Limited Options UpdateMissing authorization · CVE-2025-2816 | ≥ 2.8.0, ≤ 2.8.4 | 2.8.5 | High 8.1 | Apr 30, 2025 |
| Page View Count <= 2.6.0 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-0095 | ≤ 2.6.0 | 2.6.1 | Medium 6.4 | Jan 10, 2023 |
| Page View Count <= 2.5.5 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2022-40131 | ≤ 2.5.5 | 2.5.6 | High 8.8 | Oct 13, 2022 |
| Page Views Count Plugin <= 2.4.14 - Unauthenticated SQL InjectionSQL injection · CVE-2022-0434 | < 2.4.15 | 2.4.15 | Critical 9.8 | Feb 1, 2022 |
| Page View Counts <= 2.4.8 - Contributor+ Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-24509 | ≤ 2.4.8 | 2.4.9 | Medium 5.4 | Jul 12, 2021 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Dec 8, 2025.
Most common weaknesses in Page View Count
Missing authorization
2 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site scripting (XSS)
2 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Cross-site request forgery (CSRF)
1 issue
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is Page View Count safe to use?
Page View Count is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.9.2) and turn on automatic updates.
How do I find which version of Page View Count my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesPage View Count on WordPress.org