cve.bz

CVE-2026-125440 WordPress s2Member plugin <= 261106 - Content Injection vulnerability

5.3 mediumFix available

Medium (5.3) in cristián lávaque s2member.

On this page
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Cristián Lávaque s2Member s2member allows Code Injection.This issue affects s2Member: from n/a through 261106.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
Patchstack (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-125440 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125440?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125440?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125440 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125440

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125440](https://cve.bz/cve/badge/CVE-2026-125440.svg)](https://cve.bz/cve/CVE-2026-125440)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125440"><img src="https://cve.bz/cve/badge/CVE-2026-125440.svg" alt="CVE-2026-125440"></a>

Affected

  • cristián lávaque:s2member

Versions

From the CNA's record in the CVE List.

ProductAffected
Cristián Lávaque s2Memberthrough 261106

Fixed in

ProductFixed in
Cristián Lávaque s2Member261110

Fix and patched versions

  • Cristián Lávaque s2Member: fixed in 261110

Attack patterns (CAPEC)

  • CAPEC-18 XSS Targeting Non-Script Elements Likelihood: High · Severity: Very High
  • CAPEC-32 XSS Through HTTP Query Strings Likelihood: High · Severity: High
  • CAPEC-86 XSS Through HTTP Headers Likelihood: High · Severity: Very High
  • CAPEC-193 PHP Remote File Inclusion Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON