LiveActive security incident?Get immediate response
CVE Record

CVE-2022-33965: WordPress WP Visitor Statistics plugin <= 5.7 - Multiple Unauthenticated SQL Injection (SQLi) vulnerabilities

Multiple Unauthenticated SQL Injection (SQLi) vulnerabilities in Osamaesh WP Visitor Statistics plugin <= 5.7 at WordPress.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-33965 is a critical issue in the WP Visitor Statistics WordPress plugin. Sites running version 5.7 or older may let unauthenticated visitors manipulate database queries, potentially exposing sensitive data. The provided sources do not show active exploitation evidence.

Executive priority

Treat this as urgent for any public WordPress site using the plugin. The main business concern is potential database exposure without requiring stolen credentials or user interaction. Prioritize discovery and remediation ahead of routine website maintenance.

Technical view

The issue is multiple unauthenticated SQL injection vulnerabilities in Osamaesh WP Visitor Statistics for WordPress versions <= 5.7. It is classified as CWE-89 with CVSS 3.1 score 9.3: network-accessible, low complexity, no privileges, no user interaction, changed scope, high confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites with the WP Visitor Statistics plugin installed at version 5.7 or earlier, especially public internet-facing sites. The bundle does not identify affected CPEs or non-WordPress products.

Exploitation context

KEV status is false, and the provided sources do not cite active exploitation. Risk remains high because the vulnerability is unauthenticated, remotely reachable, and affects database query handling on public WordPress sites.

Researcher notes

The source bundle confirms affected product, version range, CWE, and CVSS but does not include exploit details, affected endpoints, or a named fixed version. Validate using inventory and vendor guidance rather than production exploit testing.

Mitigation direction

  • Inventory WordPress sites for the WP Visitor Statistics plugin.
  • Check whether installed versions are 5.7 or older.
  • Follow current vendor or WordPress plugin repository guidance for updating.
  • Disable or remove the plugin if no supported fix is available.
  • Review web and application logs for suspicious unauthenticated requests.

Validation and detection

  • Confirm plugin presence and exact version on each WordPress instance.
  • Verify remediated sites no longer run version 5.7 or older.
  • Check security scanner findings against the plugin slug and version.
  • Review database and web logs for abnormal query-related errors.
  • Document remediation status for each internet-facing site.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-33965 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N3.94.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2022-33965Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OsamaeshWP Visitor Statistics (WordPress plugin)<= 5.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.