CVE-2022-0541: Flo Launch < 2.4.1 - Missing Authentication Allow Full Site Takeover

Is it exploited?

Reported, not confirmed by CISA. VulnCheck KEV lists it as exploited in the wild. CISA has not added it to its Known Exploited Vulnerabilities catalog as of 10 Nov 2026.

VulnCheck KEV lists it since 11 Nov 2026. It cites 1 public report, the first from 11 Nov 2026.

• patchstack.com

How likely is exploitation in the next 30 days?

1.7%

EPSS score, percentile 77.6 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

Not scored

The CVE record carries no CVSS score.

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

No patch or vendor advisory is listed in the CVE record. Check the vendor's advisories.

Which versions are affected?

Affected

• from 2.4.1 to before 2.4.1

Versions by product

Source: CISA KEV 2026.11.10, as of 10 Nov 2026; VulnCheck KEV, as of 12 Nov 2026; FIRST EPSS, as of 11 Nov 2026; CVE List, as of 12 Nov 2026. About the data.

Description

Flo Launch < 2.4.1 - Missing Authentication Allow Full Site Takeover

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.

Source: CVE List, as of 12 Nov 2026. About the data.

What to do

Advisories and patches

No patch, vendor advisory or mitigation is listed in the CVE record. Check the vendor's own security advisories for a fix, and compare your version with the affected versions below.

This summary is based on the CVE record as of 12 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 12 Nov 2026. About the data.

Timeline