CVE-2022-0541

Public Exploit
Flo Launch < 2.4.1 - Missing Authentication Allow Full Site Takeover

Description

The flo-launch WordPress plugin before 2.4.1 injects code into wp-config.php when creating a cloned site, allowing any attacker to initiate a new site install by setting the flo_custom_table_prefix cookie to an arbitrary value.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.73% Top 30%
Third-Party Advisory wpscan.com
Affected: Unknown flo-launch
Published at:
Updated at:

References

Link Tags
https://wpscan.com/vulnerability/822cac2c-decd-4aa4-9e8e-1ba2d0c080ce third party advisory exploit

Frequently Asked Questions

What is the severity of CVE-2022-0541?
CVE-2022-0541 has been scored as a critical severity vulnerability.
How to fix CVE-2022-0541?
To fix CVE-2022-0541, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-0541 being actively exploited in the wild?
It is possible that CVE-2022-0541 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0541?
CVE-2022-0541 affects Unknown flo-launch.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.