dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3643

HIGH · 7.2 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Accessibly WordPress plugin has a critical Stored XSS vulnerability where unauthenticated attackers can inject arbitrary JavaScript via the REST API endpoints `/otm-ac/v1/update-widget-options` and `/otm-ac/v1/update-app-config`. These endpoints lack authentication checks (permission_callback set to __return_true) and accept user-supplied JSON that gets stored without sanitization. The widgetSrc option value is later directly used in wp_enqueue_script(), causing the injected script to execute on every front-end page.

MitigationImmediate remediation requires: 1) adding proper authentication/authorization checks to the REST API endpoints, 2) implementing server-side sanitization and validation for all option values before storage, and 3) validating the widgetSrc URL before enqueueing. Until the patch is applied, consider disabling the plugin or restricting access to these endpoints at the server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Accessibly plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Accessibly' or check the plugins directory at /wp-content/plugins/ for an 'accessibly' folder
    Affected if The Accessibly plugin is present in the WordPress installation
  2. Check installed Accessibly version
    In WordPress admin plugins list, view the plugin details to see the installed version number. Compare against any known affected version range
    Affected if The plugin version falls within a vulnerable range where the REST API endpoints lack proper authentication
  3. Test REST API endpoint accessibility
    Send a GET request to /wp-json/otm-ac/v1/update-widget-options and /wp-json/otm-ac/v1/update-app-config using curl or a browser. Check if endpoints respond without requiring authentication
    Affected if The endpoints return a response (even an error) indicating they exist and are accessible without authentication (permission_callback is __return_true)
  4. Inspect stored option values in database
    Query the wp_options table for option_name values containing 'widgetSrc' or similar using: SELECT * FROM wp_options WHERE option_name LIKE '%widget%'. Check if the option_value contains unexpected URLs or script tags
    Affected if The widgetSrc or related option contains a value that was not set through legitimate admin interface, or contains javascript: or <script> tags
  5. Check for unauthorized script enqueuing
    View page source of any frontend page and search for script tags with sources that do not match expected Accessibly functionality. Also check wp_enqueue_script calls in plugin code for unsanitized widgetSrc usage
    Affected if Scripts are being loaded from unexpected domains or the widgetSrc option is being directly enqueued without validation

A user is affected if the Accessibly plugin is installed, the REST API endpoints are accessible without authentication, and the widgetSrc option in the database contains unexpected or malicious values that get directly enqueued as scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediate remediation requires: 1) adding proper authentication/authorization checks to the REST API endpoints, 2) implementing server-side sanitization and validation for all option values before storage, and 3) validating the widgetSrc URL before enqueueing. Until the patch is applied, consider disabling the plugin or restricting access to these endpoints at the server level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3643 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data