CVE-2026-3643 json
Accessibly <= 3.0.3 - Missing Authorization to Unauthenticated Stored Cross-Site Scripting via Widget Source Injection via REST API
published 2026-04-15 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-22860
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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 `<script>` 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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- onthemapmarketing Accessibly – WordPress Website Accessibility
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/f8234ea2-ff80-425f-b83d-29c422b40c6a?source=cve
- plugins.trac.wordpress.org /browser/otm-accessibly/trunk/public/Api/BaseApiController.php#L22
- plugins.trac.wordpress.org /browser/otm-accessibly/tags/3.0.3/public/Api/BaseApiController.php#L22
- plugins.trac.wordpress.org /browser/otm-accessibly/trunk/public/admin/AdminApi.php#L65
- plugins.trac.wordpress.org /browser/otm-accessibly/tags/3.0.3/public/admin/AdminApi.php#L65
- plugins.trac.wordpress.org /browser/otm-accessibly/trunk/public/Data/AccessiblyOptions.php#L69
- plugins.trac.wordpress.org /browser/otm-accessibly/tags/3.0.3/public/Data/AccessiblyOptions.php#L69
- plugins.trac.wordpress.org /browser/otm-accessibly/trunk/public/AssetsManager.php#L63
- plugins.trac.wordpress.org /browser/otm-accessibly/tags/3.0.3/public/AssetsManager.php#L63
Sources
- CVE List CVE-2026-3643
- NVD CVE-2026-3643
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.