Remove Footer Credit < 1.0.6 - CSRF to Stored Cross-Site Scripting

published 2022-02-14 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-11358

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

The Remove Footer Credit WordPress plugin before 1.0.6 does not have CSRF check in place when saving its settings, which could allow attacker to make logged in admins change them and lead to Stored XSS issue as well due to the lack of sanitisation

Patch / fix

fixed in 1

wpchill remove_footer_credit 1.0.6

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpscan.com https://wpscan.com/vulnerability/be55131b-d9f2-4ac1-b667-c544c066887f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

Unknown Remove Footer Credit

Classification

Weakness

CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

wpscan.com /vulnerability/be55131b-d9f2-4ac1-b667-c544c066887f
exploit, third-party-advisory

Sources

CVE List CVE-2021-24446
NVD CVE-2021-24446

Fencer Vulns 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