{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12853 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12853 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12853 is a medium-severity missing authorization vulnerability in rocklobsterinc Flamingo, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12853 and fix it if it is affected.\n\nWhat it is: CVE-2026-12853 is a medium-severity missing authorization vulnerability in rocklobsterinc Flamingo, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12853 in the wild and no public exploit code.\n\nAffected product: rocklobsterinc Flamingo. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12853/ (Markdown: https://insights.sbomify.com/CVE-2026-12853/index.md)","id":"CVE-2026-12853","markdown":"https://insights.sbomify.com/CVE-2026-12853/index.md","name":"CVE-2026-12853","record":{"aliases":["GHSA-gc86-q63m-v87m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can bypass authorization to disclose internal taxonomy terms and submission counts via WordPress core APIs.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in Flamingo","id":"CVE-2026-12853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":12,"next":{"headline":"H19WMIHandlerSmm: unvalidated memory boundary could result in arbitrary code execution.","id":"CVE-2026-12855"},"packages":[],"prev":{"headline":"MLS wire decoder allocates attacker-declared opaque length before bounds check","id":"CVE-2026-12852"},"products":["Flamingo"],"published":"2026-09-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["rocklobsterinc"]},"summary":"Authenticated contributors can bypass authorization to disclose internal taxonomy terms and submission counts via WordPress core APIs.","url":"https://insights.sbomify.com/CVE-2026-12853/"}