Skip to main content
VulnerabilityPublished

CVE-2026-97347: Post Views Stats Counter (WordPress plugin) · Cross-site Scripting

Affects Post Views Stats Counter (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 12 Nov 2026, 23:25 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
kazukiyanamotoPost Views Stats CounterAffected
  • <=1.1.7
Fixed in–

AI-suggested

Users should monitor the vendor's channels for updates. Until a fix is released, consider disabling the plugin or restricting access to affected pages to trusted users only. Avoid relying on the plugin's built-in input filtering as it is insufficient to prevent exploitation.

Description

The Post Views Stats Counter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via User-Agent Header in all versions up to, and including, 1.1.7 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. The plugin's only input filter is a substring blacklist for known bot signatures (e.g. 'bot', 'spider', 'crawler'), which can be trivially bypassed by crafting a User-Agent payload that omits those strings.

References

Community reviews

Loading reviews…