Batavi before 1.0 has CSRF.

published 2020-02-05 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0545

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits: 0; none known

Patch / fix

fixed in 1

batavi batavi 1.0

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

openwall.com https://www.openwall.com/lists/oss-security/2011/01/27/3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Batavi Batavi

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

openwall.com /lists/oss-security/2011/01/27/3
exploit, mailing-list, third-party-advisory
packetstormsecurity.com /files/cve/CVE-2011-0525
broken-link

Sources

CVE List CVE-2011-0525
NVD CVE-2011-0525

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary