How severe is CVE-2024-5551?

CVE-2024-5551 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-5551 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-5551?

CVE-2024-5551 affects Wp-staging Wp Staging. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-5551?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-5551 have an EU (EUVD) identifier?

Yes. CVE-2024-5551 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-46750.

When was CVE-2024-5551 published?

CVE-2024-5551 was published on 2024-06-14 and last updated on 2026-06-17.

CVE-2024-5551

CVE-2024-5551 is a high-severity vulnerability in Wp-staging Wp Staging with a CVSS 3.x base score of 7.5. 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

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-46750
Weakness: CWE-352
Affected product: Wp-staging Wp Staging
Published: 2024-06-14
Last modified: 2026-06-17

Description

The WP STAGING Pro WordPress Backup Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.6.0. This is due to missing or incorrect nonce validation on the 'sub' parameter called from the WP STAGING WordPress Backup Plugin - Backup Duplicator & Migration plugin. This makes it possible for unauthenticated attackers to include any local files that end in '-settings.php' via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Frequently asked questions

What is CVE-2024-5551?: The WP STAGING Pro WordPress Backup Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.6.0. This is due to missing or incorrect nonce validation on the 'sub' parameter called from the WP STAGING WordPress Backup Plugin - Backup Duplicator & Migration plugin. This makes it possible for unauthenticated attackers to include any local files that end in '-settings.php' via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
How severe is CVE-2024-5551?: CVE-2024-5551 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-5551 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-5551?: CVE-2024-5551 affects Wp-staging Wp Staging. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-5551?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-5551 have an EU (EUVD) identifier?: Yes. CVE-2024-5551 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-46750.
When was CVE-2024-5551 published?: CVE-2024-5551 was published on 2024-06-14 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:wp-staging:wp_staging:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Wp-staging Wp Staging

CVE-2024-4469 — High (CVSS 7.5): The WP STAGING WordPress Backup Plugin WordPress plugin before 3.5.0 does not prevent users with the administrator…
CVE-2023-7204 — High (CVSS 7.5): The WP STAGING WordPress Backup plugin before 3.2.0 allows access to cache files during the cloning process which…
CVE-2023-6113 — High (CVSS 7.5): The WP STAGING WordPress Backup Plugin before 3.1.3 and WP STAGING Pro WordPress Backup Plugin before 5.1.3 do not…
CVE-2024-2309 — Medium (CVSS 4.8): The WP STAGING WordPress Backup Plugin WordPress plugin before 3.4.0, wp-staging-pro WordPress plugin before 5.4.0…
CVE-2022-2737 — Medium (CVSS 4.8): The WP STAGING WordPress plugin before 2.9.18 does not sanitise and escape some of its settings, which could allow high…

All CVEs affecting Wp-staging Wp Staging →

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

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

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