Is WP-Stats safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.0.1). As of 2026-11-04. 3 issues are on record for older versions; version 2.56.1 or newer fixes all of them that state a fix. Keep WP-Stats on the latest version (3.0.1) and remove it if you do not use it.

Which versions of WP-Stats are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (2.56 and older, fixed in 2.56.1); Cross-site scripting (XSS) (2.56 and older, fixed in 2.56.1); Cross-site request forgery (CSRF) (older than 2.52, fixed in 2.52). The full list with sources is on this page.

What is the latest version of WP-Stats?

3.0.1, according to wordpress.org (last updated 2026-09-01). It has 2,000+ active installs.

What should I do if my WP-Stats is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-stats). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-stats · data as of 2026-11-04

Is WP-Stats safe? Known vulnerabilities and latest version

Latest version: 3.0.1
Last updated: 2026-09-01
Active installs: 2,000+
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 8.2+

Display your WordPress blog statistics. Ranging from general total statistics, some of my plugins statistics and top 10 statistics. — by Lester Chan

What to do

Update to the latest version (3.0.1). Anything older than 2.56.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get wp-stats --field=version shows what you run; wp plugin update wp-stats updates it.

Check your version

Known vulnerabilities

3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.2 CVE-2026-19794 · published 2026-08-14

Stored cross-site scripting (XSS) in WP-Stats (2.56 and older)

Affected: 2.56 and older
Fixed in: 2.56.1 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The WP-Stats plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.56 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2026-19794 Wordfence advisory Patchstack advisory

high 7.1 CVE-2026-66426 · published 2026-08-13

Cross-site scripting (XSS) in WP-Stats (2.56 and older)

Affected: 2.56 and older
Fixed in: 2.56.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Cross Site Scripting (XSS) in WP-Stats <= 2.56 versions.

NVD CVE-2026-66426 Patchstack advisory

medium 4.3 CVE-2015-10001 · published 2021-11-01

Cross-site request forgery (CSRF) in WP-Stats (older than 2.52)

Affected: older than 2.52
Fixed in: 2.52
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

The WP-Stats WordPress plugin before 2.52 does not have CSRF check when saving its settings, and did not escape some of them when outputting them, allowing attacker to make logged in high privilege users change them and set Cross-Site Scripting payloads

NVD CVE-2015-10001 WPScan advisory openwall.com

Recent activity

2026-09-01 — latest release on wordpress.org (3.0.1).
2026-08-14 — Stored cross-site scripting (XSS) disclosed (CVE-2026-19794), fixed in 2.56.1.
2026-08-13 — Cross-site scripting (XSS) disclosed (CVE-2026-66426), fixed in 2.56.1.
2021-11-01 — Cross-site request forgery (CSRF) disclosed (CVE-2015-10001), fixed in 2.52.

Free. We check the CVE feeds every day and email you only when a new issue for WP-Stats (wp-stats) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (2) · Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-stats (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-stats"><img src="https://laskyr.com/plugins/wp-stats/badge.svg" alt="WP-Stats vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is WP-Stats safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.0.1)

What to do

Check your version

Known vulnerabilities

Stored cross-site scripting (XSS) in WP-Stats (2.56 and older)

Cross-site scripting (XSS) in WP-Stats (2.56 and older)

Cross-site request forgery (CSRF) in WP-Stats (older than 2.52)

Recent activity

Get an email when WP-Stats has a new vulnerability

Browse vulnerabilities

Where this data comes from