Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress Kento Splash Screen plugin through version 1.4. A malicious site could abuse missing request protection to make a legitimate user save attacker-controlled script into the site. Business risk is highest for WordPress sites that still run this plugin, because stored script can affect trust, content integrity, and users.
Executive priority
Treat as a high-priority WordPress plugin exposure check. It is not currently supported by provided evidence as actively exploited, but stored XSS can create customer-facing and administrative risk if the vulnerable plugin remains deployed.
Technical view
The issue is a CSRF vulnerability in PluginsPoint Kento Splash Screen that can result in stored XSS. CVSS 3.1 is 7.1: network reachable, low complexity, no attacker privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact. The provided sources do not describe the exact vulnerable endpoint or storage location.
Likely exposure
Exposure is limited to WordPress installations with Kento Splash Screen installed and active at version 1.4 or earlier. Sites without this plugin are not indicated as affected. The source bundle does not identify a fixed version or vendor patch status.
Exploitation context
The CVE is not listed as CISA KEV in the provided data, and no cited source states active exploitation. Exploitation requires user interaction, consistent with CSRF, and may depend on tricking a legitimate site user into performing an unwanted action.
Researcher notes
Evidence is thin beyond the CVE metadata and Patchstack entry. Do not assume affected endpoints, payloads, exploit maturity, or patch availability from the provided bundle. Validation should focus on plugin presence, version, activation state, and official remediation updates.
Mitigation direction
Inventory WordPress sites for the Kento Splash Screen plugin and version.
Check vendor or Patchstack guidance for a fixed release or official workaround.
Disable or remove the plugin if no trusted fixed version is available.
Restrict WordPress administrative access to trusted users and hardened sessions.
Monitor affected sites for unexpected splash screen or content changes.
Validation and detection
Confirm whether kento-splash-screen is installed and active on each WordPress site.
Record plugin version and flag any instance at 1.4 or earlier.
Review WordPress admin activity around plugin configuration changes.
Inspect affected pages for unexpected stored script or altered splash screen content.
Track CVE and Patchstack entries for updated remediation details.
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-352: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.