dbcve.org
Enable AccessibilityWordPress extension · Upress

CVE-2023-30484

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in uPress Enable Accessibility plugin <= 1.4 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the uPress Enable Accessibility WordPress plugin versions 1.4 and below allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.

MitigationImplement anti-CSRF tokens or unique request identifiers for state-changing operations and validate the Referer or Origin header to ensure requests originate from trusted sources.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enable AccessibilityWordPress extension
Affected:<= 1.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check if Upress Enable Accessibility plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'enable-accessibility' or similar
    Affected if plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    In WordPress admin, find the plugin in the Plugins list and look for the version number under the plugin name, or open the main plugin PHP file and check the Version header in the plugin comment block
    Affected if version displayed is 1.4 or lower, or version cannot be determined (older/unmaintained plugin)
  3. Verify the plugin handles state-changing operations
    Review the plugin functionality - check if it includes features that modify site settings, user preferences, accessibility options, or any action that changes data in the database
    Affected if plugin contains any features that create, modify, or delete data (state-changing operations)
  4. Confirm authentication is required for vulnerable actions
    Check the affected URL endpoints or forms within the plugin - determine if they require a logged-in user with appropriate privileges to submit requests
    Affected if plugin actions can be performed by authenticated users without anti-CSRF tokens

If the Upress Enable Accessibility plugin is installed with version 1.4 or lower and handles any state-changing operations that lack CSRF protection, the environment is vulnerable to CVE-2023-30484.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.4
Interim mitigation

Implement anti-CSRF tokens or unique request identifiers for state-changing operations and validate the Referer or Origin header to ensure requests originate from trusted sources.

Recommended fix Moderate confidence

1.5 or later (update to latest available version)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Enable Accessibility' plugin by uPress
  4. 4. Check if an update is available and update to the latest version
  5. 5. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enable Accessibility 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 the upgrade done

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-2023-30484 — 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-2023-30484 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