{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3643 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3643 is a high-severity cross-site scripting vulnerability in onthemapmarketing Accessibly – WordPress Website Accessibility, published on 15 Apr 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-3643 and fix it if it is affected.\n\nWhat it is: CVE-2026-3643 is a high-severity cross-site scripting vulnerability in onthemapmarketing Accessibly – WordPress Website Accessibility, published on 15 Apr 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-3643 in the wild and no public exploit code.\n\nAffected product: onthemapmarketing Accessibly – WordPress Website Accessibility. 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-3643/ (Markdown: https://insights.sbomify.com/CVE-2026-3643/index.md)","id":"CVE-2026-3643","markdown":"https://insights.sbomify.com/CVE-2026-3643/index.md","name":"CVE-2026-3643","record":{"aliases":["GHSA-7xm7-cgqr-v2h2"],"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 malicious JavaScript via REST API endpoints, leading to stored XSS execution for all site visitors.","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 Accessibly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API in all versions up to, and including, 3.0.3. The plugin registers REST API endpoints at `/otm-ac/v1/update-widget-options` and `/otm-ac/v1/update-app-config` with the `permission_callback` set to `__return_true`, which means no authentication or authorization check is performed. The `updateWidgetOptions()` function in `AdminApi.php` accepts user-supplied JSON data and passes it directly to `AccessiblyOptions::updateAppConfig()`, which saves it to the WordPress options table via `update_option()` without any sanitization or validation. The stored `widgetSrc` value is later retrieved by `AssetsManager::enqueueFrontendScripts()` and passed directly to `wp_enqueue_script()` as the script URL, causing it to be rendered as a `\u003cscript\u003e` tag on every front-end page. This makes it possible for unauthenticated attackers to inject arbitrary JavaScript that executes for all site visitors by changing the `widgetSrc` option to point to a malicious external script.","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":"Cross-site scripting in Accessibly – WordPress Website Accessibility","id":"CVE-2026-3643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Incomplete control character validation in http.cookies","id":"CVE-2026-3644"},"packages":[],"prev":{"headline":"e-shot \u003c= 1.0.2 - Missing Authorization to Authenticated (Subscriber+) Form Settings Modification via AJAX","id":"CVE-2026-3642"},"products":["Accessibly – WordPress Website Accessibility"],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["onthemapmarketing"]},"summary":"Unauthenticated attackers can inject malicious JavaScript via REST API endpoints, leading to stored XSS execution for all site visitors.","url":"https://insights.sbomify.com/CVE-2026-3643/"}