Plugins · visit-counter · data as of 2026-11-04
Is Visit Counter safe? Known vulnerabilities and latest version
- Status
- Closed 2025-10-31
- Known issues on record
- 2
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate visit-counter && wp plugin delete visit-counter
Check your version
Known vulnerabilities
2 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. 2 record(s) do not state which versions are affected.
medium 6.1 CVE-2025-12452 · published 2025-11-04
Cross-site request forgery (CSRF) in Visit Counter (1.0 only)
- Affected
- 1.0 only
- Fixed in
- unknown
- 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 Wordfence
Details from the advisory
The Visit Counter plugin for WordPress is vulnerable to Cross-Site Request Forgery in version 1.0. This is due to missing or incorrect nonce validation on the widgets.php page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
high 7.1 CVE-2025-49065 · published 2025-08-14
Stored cross-site scripting (XSS) in Visit Counter (1.0 and older)
- Affected
- 1.0 and older
- Fixed in
- unknown
- 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in BestiaDurmiente Visit Counter visit-counter allows Stored XSS.This issue affects Visit Counter: from n/a through <= 1.0.
Recent activity
- 2025-10-31 — closed on wordpress.org (Security Issue).
- 2025-11-04 — Cross-site request forgery (CSRF) disclosed (CVE-2025-12452), fix version not stated.
- 2025-08-14 — Stored cross-site scripting (XSS) disclosed (CVE-2025-49065), fix version not stated.
Get an email when Visit Counter has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Visit Counter (visit-counter) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site request forgery (CSRF) (1) · Cross-site scripting (XSS) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/visit-counter (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/visit-counter"><img src="https://laskyr.com/plugins/visit-counter/badge.svg" alt="Visit Counter vulnerability status"></a>