dbcve.org
Wp StatisticsWordPress extension · Veronalabs

CVE-2022-27231

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-13
Fix available
A fix is available. Upgrade to 13.2.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting vulnerability exists in WP Statistics versions prior to 13.2.0 because it improperly processes a platform parameter. By exploiting this vulnerability, an arbitrary script may be executed on the web browser of the user who is logging in to the website using the product.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in the WP Statistics WordPress plugin. The plugin improperly processes a platform parameter, allowing an attacker to inject malicious JavaScript that executes in the browser of users logging into the affected website.

MitigationUpdate WP Statistics to version 13.2.0 or later to receive the patch that properly sanitizes the platform parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp StatisticsWordPress extension
Affected:< 13.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Statistics plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Statistics' by Veronalabs, or check the /wp-content/plugins/wp-statistics/ directory exists on the server
    Affected if WP Statistics plugin is not found on the system
  2. Identify installed WP Statistics version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under WP Statistics, or read the version from the plugin's main PHP file header in /wp-content/plugins/wp-statistics/
    Affected if No version number is displayed or the plugin file cannot be located
  3. Compare installed version to affected range
    Check if the installed version is less than 13.2.0 (for example: 13.1.9, 13.0.0, 12.6.5, etc.)
    Affected if Installed version is a number lower than 13.2.0 (e.g., 13.1.x, 13.0.x, 12.x, etc.)
  4. Confirm the platform parameter is in use
    The plugin must have the 'platform' parameter functionality enabled. This typically relates to the plugin's tracking settings that record the platform (browser/OS) of visitors. Check if the plugin's statistics tracking features are active in the plugin settings.
    Affected if The plugin's platform/visitor tracking feature is enabled and the installed version is below 13.2.0

The environment is affected if WP Statistics plugin version is below 13.2.0 and the platform/visitor tracking feature is active, allowing stored XSS via the platform parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.2.0 or later
Fixed in 13.2.0
Interim mitigation

Update WP Statistics to version 13.2.0 or later to receive the patch that properly sanitizes the platform parameter.

Recommended fix High confidence

WP Statistics 13.2.0

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find WP Statistics in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 13.2.0 from wordpress.org/plugins/wp-statistics/
  5. Verify the plugin version shows 13.2.0 or higher after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Statistics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27231 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data