LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1238: SlimStat Analytics <= 5.3.5 - Unauthenticated Stored Cross-Site Scripting via 'fh'

The SlimStat Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'fh' (fingerprint) parameter in all versions up to, and including, 5.3.5 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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-1238 affects the SlimStat Analytics WordPress plugin through version 5.3.5. An unauthenticated attacker can store malicious script through the fingerprint parameter. That script may run in a user’s browser when the affected page is viewed, risking session abuse, content manipulation, or credential exposure within the site context.

Executive priority

Prioritize remediation for public WordPress sites, especially those with administrator activity or sensitive user sessions. This is not confirmed exploited in the provided sources, but unauthenticated stored XSS in a common web platform warrants prompt action.

Technical view

The issue is stored cross-site scripting in SlimStat Analytics via insufficient sanitization and output escaping of the 'fh' parameter. The CVE assigns CVSS 7.2, CWE-79, network attack vector, low complexity, and no privileges required. Public references include vulnerable code locations and a WordPress plugin changeset.

Likely exposure

Internet-facing WordPress sites using SlimStat Analytics versions up to and including 5.3.5 are the likely exposure. The provided affected metadata is inconsistent, so confirm against installed plugin versions and vendor records.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk remains meaningful because the attack is unauthenticated and stored, allowing script execution later when affected content is viewed.

Researcher notes

Source data names versions through 5.3.5 but does not explicitly name a fixed version. The WordPress Trac changeset is relevant for code review. Avoid assuming exploitation in the wild without KEV or additional cited intelligence.

Mitigation direction

  • Identify all WordPress sites running SlimStat Analytics.
  • Check vendor or WordPress plugin guidance for the fixed release.
  • Upgrade to a release containing the referenced sanitization/escaping changes.
  • Disable the plugin if no validated update is available.
  • Review web application firewall rules for this CVE if available.

Validation and detection

  • Confirm installed SlimStat Analytics version on each WordPress site.
  • Flag versions up to and including 5.3.5 for remediation.
  • Review access logs for suspicious use of the 'fh' parameter.
  • Confirm updated code includes input sanitization and output escaping changes.
  • Retest affected pages for stored script execution after remediation.
Prepared
Confidence
medium
Sources
6

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2026-1238 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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
5Source 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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-1238Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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
veronalabsSlimStat Analytics0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.