CVE-2025-1436: The Limit Bio WordPress plugin through 1.0 does not have CSRF check when updating its settings, and is missing

Routine

HIGH 7.1DOWNGRADE

CVE-2025-1436 is a high-severity flaw (CVSS 7.1) affecting limit bio. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-352
Published	2025-03-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: rivercitygraphix

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-13 06:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

rivercitygraphix limit bio DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy limit-bio || rpm -q limit-bio || limit-bio --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison limit-bio sudo apt install limit-bio=<VERSION_BEFORE_1.0> sudo apt-mark hold limit-bio

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list limit-bio sudo dnf downgrade limit-bio-<VERSION_BEFORE_1.0> sudo dnf versionlock add limit-bio

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1436?

limit bio: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-1436 being exploited?

CVE-2025-1436 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1436 affect?

CVE-2025-1436 affects limit bio. Severity is high (CVSS 7.1). 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.

How urgent is CVE-2025-1436?

Priority 31/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-13884 HIGH 7.1 DOWNGRADE The Limit Bio WordPress plugin through 1.0 does not sanitise and escape a parameter before outputting it back

References

← Back to latest CVEs