Wp StatisticsWordPress extension · Veronalabs
CVE-2022-38074
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 · uneditedSQL Injection vulnerability in VeronaLabs WP Statistics plugin <= 13.2.10 versions.
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 · moderate confidenceSQL Injection vulnerability in the VeronaLabs WP Statistics WordPress plugin versions 13.2.10 and below allows attackers to inject malicious SQL statements through unsanitized user inputs, potentially enabling unauthorized data access, modification, or exfiltration from the WordPress database.
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
< 13.2.11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify WP Statistics plugin versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins > WP Statistics and note the version number displayedAffected if The displayed version is 13.2.10 or lower
-
Verify plugin is activeCheck the Plugins list in WordPress admin to confirm WP Statistics status shows as ActiveAffected if The plugin is active and the version is 13.2.10 or below
-
Check plugin file version directlyAccess the server file system and open wp-content/plugins/wp-statistics/wp-statistics.php, read the Version field from the plugin header comment blockAffected if The version string in the file header reads 13.2.10 or lower
If the WP Statistics plugin is installed with version 13.2.10 or below and is active, the environment is vulnerable to CVE-2022-38074
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.2.11
Upgrade the WP Statistics plugin to a version newer than 13.2.10, or apply the vendor patch if available. If immediate upgrade is not possible, restrict access to the affected plugin endpoints via web application firewall rules.
WP Statistics 13.2.11
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins
- Find WP Statistics plugin and check for available updates
- Update WP Statistics to version 13.2.11 or later
- Verify the update was successful by checking the plugin version
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
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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