{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6177 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6177 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6177 is a high-severity cross-site scripting vulnerability in smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6177 and fix it if it is affected.\n\nWhat it is: CVE-2026-6177 is a high-severity cross-site scripting vulnerability in smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6177 in the wild and no public exploit code.\n\nAffected product: smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget. 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-6177/ (Markdown: https://insights.sbomify.com/CVE-2026-6177/index.md)","id":"CVE-2026-6177","markdown":"https://insights.sbomify.com/CVE-2026-6177/index.md","name":"CVE-2026-6177","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary web scripts via cached tweet text in the Custom Twitter Feeds WordPress plugin.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Custom Twitter Feeds plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 2.5.4. This is due to insufficient output escaping in the CTF_Display_Elements::get_post_text() function when rendering cached tweet text. The plugin's ctf_get_more_posts AJAX action is available to unauthenticated users and directly outputs cached tweet data through nl2br() without HTML escaping. When an attacker can get malicious content into cached tweet data (either by tweeting content that gets cached by the site's feed configuration, or through other vulnerabilities), the malicious HTML/JavaScript is executed when the unauthenticated endpoint is accessed. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the affected endpoint.","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":"Custom Twitter Feeds \u003c= 2.5.4 - Unauthenticated Stored Cross-Site Scripting via Cached Tweet Text","id":"CVE-2026-6177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Betheme \u003c= 28.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'icon_box_2' Shortcode","id":"CVE-2026-6178"},"packages":[],"prev":{"headline":"Customer Reviews for WooCommerce \u003c= 5.106.0 - Unauthenticated Stored Cross-Site Scripting via Aggregated Review Form","id":"CVE-2026-6176"},"products":["Custom Twitter Feeds – A Tweets Widget or X Feed Widget"],"published":"2026-05-13","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["smub"]},"summary":"Unauthenticated attackers can inject arbitrary web scripts via cached tweet text in the Custom Twitter Feeds WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-6177/"}