Skip to content
Laskyr

Plugins · flamingo · data as of 2026-11-01

Is Flamingo safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.6.4)

As of 2026-11-01. 1 issue is on record for older versions; version 2.6.3 or newer fixes all of them that state a fix.

Latest version
2.6.4
Last updated
2026-08-18
Active installs
800,000+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.4+

A trustworthy message storage plugin for Contact Form 7. — by Rock Lobster Inc.

What to do

  1. Update to the latest version (2.6.4). Anything older than 2.6.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get flamingo --field=version shows what you run; wp plugin update flamingo updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 5.4 CVE-2026-12853 · published 2026-09-07

Missing authorization check in Flamingo (2.6.2 and older)

Affected
2.6.2 and older
Fixed in
2.6.3 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Flamingo plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.6.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to enumerate taxonomy terms including channel names derived from Contact Form 7 form titles that may reveal internal form purposes, department names, or workflow identifiers, as well as submission counts per channel and contact tag names. The plugin's flamingo_map_meta_cap() filter restricts access to Flamingo's admin UI but does not extend to WordPress core APIs such as XML-RPC wp.getTerms and admin-ajax ajax-tag-search.

NVD CVE-2026-12853Wordfence advisoryCode change (fix)Plugin source

Recent activity

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Flamingo vulnerability status badge
<a href="https://laskyr.com/plugins/flamingo"><img src="https://laskyr.com/plugins/flamingo/badge.svg" alt="Flamingo vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Site hacked? Get help now
Run free scan Fix it now ($499) Send a message

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit