CVE
Team Members stored XSS via social link URL in instant preview
- Exploited
- No known exploitation
- Fix
- Fixed in 5.4.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.4.2.
Summary
The Team Members WordPress plugin before 5.4.2 does not properly escape team member social link URLs when they are rendered back in the administration area, allowing users with the Contributor role and above to perform Stored Cross-Site Scripting attacks against higher privileged users who edit the team.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.8/10CVSS 6.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.4.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-97330 (Team Members < 5.4.2 - Contributor+ Stored XSS via Member Social Link URL in Instant Preview), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-97330 (entry last updated 2026-11-18):
Affected:
- Unknown Team Members: fixed in 5.4.2
Fixed versions: 5.4.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-97330 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-97330 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-97330
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-97330
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-97330"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Unknown Team Members
fixed in 5.4.2
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-97330 |
| Record | NVD · CVE-2026-97330 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/4e6e1a48-5385-46e7-9965-8522114ff136 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97330
Is CVE-2026-97330 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-97330?
Team Members: before 5.4.2.Source: cve.now feed data
How do I fix CVE-2026-97330?
Upgrade to a fixed version: 5.4.2.Source: cve.now feed data