CSRF in Facebook

CVE-2021-24218

The wp_ajax_save_fbe_settings and wp_ajax_delete_fbe_settings AJAX actions of the Facebook for WordPress plugin before 3.0.4 were vulnerable to CSRF due to a lack of nonce protection. The settings in the saveFbeSettings function had no sanitization allowing for script tags to be saved.

Vulnerability class: CSRF (Cross-Site Request Forgery)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.007 (51.2th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 51st percentile — 51.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2021-24218: held from 0.007 to 0.007.

EPSS over last 30 days · oldest: 0.007 · newest: 0.007 · change: 0.000

Affected products

  • Facebook
  • Facebook For WordPress — versions 3.0.0, 3.0.4

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2021-24218?
CVE-2021-24218 is a high-severity vulnerability in Facebook, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2021-04-12.
How severe is CVE-2021-24218?
High severity. CVSS v3 base score is 8.8 out of 10.
Is CVE-2021-24218 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.