Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in fyljp SpiderDisplay spiderdisplay allows Reflected XSS.This issue affects SpiderDisplay: from n/a through <= 1.9.1.
Security readout for executives and security teams
Plain-English summary
CVE-2025-23855 is a reflected cross-site scripting issue in the WordPress SpiderDisplay plugin through version 1.9.1. An attacker could trick a user into opening a crafted link, causing script to run in that user’s browser. This can affect confidentiality, integrity, and availability at a limited level.
Executive priority
Prioritize review on public WordPress sites, especially those with logged-in administrative users. This is not confirmed exploited in the supplied sources, but the score and no-auth requirement make timely assessment appropriate.
Technical view
The CVE describes CWE-79 improper input neutralization during web page generation in fyljp SpiderDisplay. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges required, and user interaction required. Scope is changed, with low confidentiality, integrity, and availability impact. Sources do not provide payload details or a confirmed fixed version.
Likely exposure
WordPress sites using the SpiderDisplay plugin at version 1.9.1 or earlier should be considered potentially exposed. Exposure depends on whether the vulnerable plugin is installed and reachable to users.
Exploitation context
The attack requires a victim to interact with a crafted request or link. The provided sources do not indicate known active exploitation, and the CVE is not marked KEV in the supplied bundle.
Researcher notes
Evidence is limited to the CVE record and Patchstack reference. The bundle states affected through 1.9.1, but the structured affected entry is sparse. No exploit status, exploit details, or fixed version are provided in the supplied material.
Mitigation direction
Inventory WordPress sites for the SpiderDisplay plugin.
Identify installed SpiderDisplay versions and flag 1.9.1 or earlier.
Check vendor, WordPress plugin, or Patchstack guidance for an update or workaround.
Disable or remove the plugin if it is unused or cannot be secured.
Review web application security controls for reflected XSS detection and blocking.
Validation and detection
Confirm whether SpiderDisplay is installed on each WordPress instance.
Record the installed plugin version from WordPress administration or asset inventory.
Compare findings against the CVE affected range: through 1.9.1.
Check Patchstack and vendor sources for fixed-version information.
Review logs for unusual requests targeting SpiderDisplay pages or parameters.
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.
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.
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.