CVE-2026-3643

| EUVD-2026-22860 HIGH
2026-04-15 Wordfence
7.2
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

1
Analysis Generated
Apr 15, 2026 - 09:09 vuln.today

DescriptionNVD

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.

AnalysisAI

Stored XSS in Accessibly WordPress plugin (≤3.0.3) allows unauthenticated attackers to inject malicious JavaScript executed by all site visitors via unprotected REST API endpoints. Two endpoints (/otm-ac/v1/update-widget-options and /otm-ac/v1/update-app-config) lack authentication checks (permission_callback set to __return_true), enabling attackers to modify the widgetSrc option with a URL pointing to attacker-controlled scripts. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: disable the Accessibly plugin immediately via WordPress admin dashboard or by renaming the plugin directory; audit WordPress options table for suspicious widgetSrc entries modified after plugin installation. Within 7 days: update to Accessibly version 3.0.4 or later when available, or identify and deploy an alternative accessibility plugin; review server logs for suspicious REST API calls to /otm-ac/v1/update-widget-options and /otm-ac/v1/update-app-config endpoints. …

Sign in for detailed remediation steps.

Share

CVE-2026-3643 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy