Flamingo · Security record
Is Flamingo safe?
No known vulnerability affects the current version (2.6.4). 4 issues were found in earlier versions and fixed, the latest disclosed on Jan 28, 2020.
Checked 3 days ago against the WPVulnerability database, for version 2.6.4.
How it’s looked after
- Last release
- Aug 18, 2026 (2 months ago)
- Releases in the last year
- 4
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 800K+
4 known vulnerabilities
- 1 medium
- 3 not rated
None affects the current version.
Every known vulnerability in Flamingo
Newest first, with any that affect the current version at the top.
Fixed in 2.1.1 · Jan 28, 2020 · Patchstack
Fixed in 2.6.3 · CVE-2026-12853 · Jan 15, 2020 · Wordfence
Fixed in 2.1.1 · Jan 15, 2020 · Wordfence
Fixed in 2.1.1 · WPScan
Questions about Flamingo’s security
Is Flamingo safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Flamingo updated: most attacks target sites that haven’t updated.
Does Flamingo have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Flamingo up to date.
Is Flamingo still maintained?
Yes. Its last release was 2 months ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is Flamingo compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.