{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3659 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3659 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3659 is a medium-severity cross-site scripting vulnerability in bappidgreat WP Circliful, published on 15 Apr 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-3659 and fix it if it is affected.\n\nWhat it is: CVE-2026-3659 is a medium-severity cross-site scripting vulnerability in bappidgreat WP Circliful, published on 15 Apr 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-3659 in the wild and no public exploit code.\n\nAffected product: bappidgreat WP Circliful. 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-3659/ (Markdown: https://insights.sbomify.com/CVE-2026-3659/index.md)","id":"CVE-2026-3659","markdown":"https://insights.sbomify.com/CVE-2026-3659/index.md","name":"CVE-2026-3659","record":{"aliases":["GHSA-jxvc-xjm6-c4gc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can inject arbitrary scripts via shortcode attributes in WP Circliful, leading to code execution in victim browsers.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 WP Circliful plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' shortcode attribute of the [circliful] shortcode and via multiple shortcode attributes of the [circliful_direct] shortcode in all versions up to and including 1.2. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. Specifically, in the circliful_shortcode() function, the 'id' attribute value is concatenated directly into an HTML id attribute (line 285) without any escaping, allowing an attacker to break out of the double-quoted attribute and inject arbitrary HTML event handlers. Similarly, the circliful_direct_shortcode() function (line 257) outputs all shortcode attributes directly into HTML data-* attributes without escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","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":"WP Circliful \u003c= 1.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'id' Shortcode Attribute","id":"CVE-2026-3659","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"IBM Engineering Lifecycle Management - Jazz Foundation is vulnerable to Authentication Bypass","id":"CVE-2026-3660"},"packages":[],"prev":{"headline":"Appointment Booking Calendar \u003c= 1.6.10.0 - Unauthenticated SQL Injection via 'fields' Parameter","id":"CVE-2026-3658"},"products":["WP Circliful"],"published":"2026-04-15","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-04-15","vendors":["bappidgreat"]},"summary":"Authenticated attackers can inject arbitrary scripts via shortcode attributes in WP Circliful, leading to code execution in victim browsers.","url":"https://insights.sbomify.com/CVE-2026-3659/"}