LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31083: WordPress Leaky Paywall plugin <= 4.21.7 - Cross Site Scripting (XSS) Vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ZEEN101 Leaky Paywall leaky-paywall allows Stored XSS.This issue affects Leaky Paywall: from n/a through <= 4.21.7.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31083 is a stored cross-site scripting issue in the WordPress Leaky Paywall plugin through version 4.21.7. A lower-privileged user may be able to store malicious web content that runs when another user views it, creating risk to sessions, content integrity, and site trust.

Executive priority

Handle in normal vulnerability remediation cycles, faster for public WordPress sites with multiple content contributors or customer-facing paywall workflows. There is no source-backed evidence of active exploitation, but stored XSS can affect user trust and administrative sessions.

Technical view

The issue is CWE-79 improper neutralization during page generation in ZEEN101 Leaky Paywall. CVSS 3.1 is 6.5 with network attack vector, low complexity, low privileges required, user interaction required, and changed scope. The source bundle does not identify the vulnerable parameter, exploit method, or fixed version.

Likely exposure

Exposure is likely limited to WordPress sites running ZEEN101 Leaky Paywall version 4.21.7 or earlier. Sites without the plugin, or with versions vendor-confirmed unaffected, are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. Stored XSS still matters because it can persist in site data and trigger when a victim views affected content, but the sources require low privileges and user interaction.

Researcher notes

The available bundle confirms product, version boundary, CWE, and CVSS vector, but lacks vulnerable endpoint, field, proof of concept, fix version, or workaround. Avoid assuming exploitability beyond stored XSS with low privileges and required user interaction.

Mitigation direction

  • Inventory WordPress sites using Leaky Paywall and record installed versions.
  • Check ZEEN101, WordPress.org, or Patchstack guidance for a fixed release or workaround.
  • Upgrade only to a vendor-supported fixed version when identified.
  • Limit plugin management privileges to trusted users while remediation is pending.
  • Review stored site content for unexpected scripts after remediation.

Validation and detection

  • Confirm whether Leaky Paywall is installed on each WordPress site.
  • Verify installed versions are above 4.21.7 or vendor-confirmed unaffected.
  • Review user roles that can create or edit Leaky Paywall content.
  • Check security monitoring for suspicious stored script activity.
  • Retest affected pages after vendor-directed remediation.
Prepared
Confidence
medium
Sources
3

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-2025-31083 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-31083Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
ZEEN101Leaky Paywallleaky-paywall, 0unaffected
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.