CVE-2024-43269

CVE-2024-43269 is a medium-severity vulnerability in Wpbackitup Backup And Restore Wordpress with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

Cross-Site Request Forgery (CSRF) vulnerability in WPBackItUp Backup and Restore WordPress.This issue affects Backup and Restore WordPress: from n/a through 1.50.

Frequently asked questions

What is CVE-2024-43269?
Cross-Site Request Forgery (CSRF) vulnerability in WPBackItUp Backup and Restore WordPress.This issue affects Backup and Restore WordPress: from n/a through 1.50.
How severe is CVE-2024-43269?
CVE-2024-43269 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2024-43269 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-43269?
CVE-2024-43269 affects Wpbackitup Backup And Restore Wordpress. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-43269?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-43269 have an EU (EUVD) identifier?
Yes. CVE-2024-43269 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-40161.
When was CVE-2024-43269 published?
CVE-2024-43269 was published on 2024-08-26 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Wpbackitup Backup And Restore Wordpress

All CVEs affecting Wpbackitup Backup And Restore Wordpress →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →