A CSRF issue was discovered in Jirafeau before 3.4.1.

published 2018-07-06 8y ago modified 2026-06-17 4mo ago also EUVD-2018-5350

cvss: 4.9; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits: 0; none known

A CSRF issue was discovered in Jirafeau before 3.4.1. The "delete file" feature on the admin panel is not protected against automated requests and could be abused.

Patch / fix

fixed in 1

jirafeau jirafeau 3.4.1

Is CVE-2018-13407 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

Exploits and checks

bishopfox.com https://www.bishopfox.com/news/2018/06/jirafeau-version-3-3-0-multiple-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	4.9	CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:N/I:P/A:P

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

bishopfox.com /news/2018/06/jirafeau-version-3-3-0-multiple-vulnerabilities/
exploit, third-party-advisory

Sources

CVE List CVE-2018-13407
NVD CVE-2018-13407

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.