dbcve.org
All In One SeoWordPress extension · Aioseo

CVE-2023-0586

MEDIUM · 5.4 CVSS v3.1 Published 2023-02-24
Fix available
A fix is available. Upgrade to after 4.2.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 All in One SEO Pack plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple parameters in versions up to, and including, 4.2.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with Contributor+ role to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

The All in One SEO Pack WordPress plugin versions up to 4.2.9 contain a stored XSS vulnerability due to insufficient input sanitization and output escaping on multiple parameters. Authenticated attackers with Contributor-level or higher permissions can inject arbitrary JavaScript into plugin settings that will execute in the browsers of users accessing affected pages.

MitigationUpdate the All in One SEO Pack plugin to a version newer than 4.2.9. Until the update is applied, limit the Contributor role permissions and review existing plugin configurations for injected malicious scripts.

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
All In One SeoWordPress extension
Affected:<= 4.2.9

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 the installed Aioseo plugin version
    In WordPress admin, go to Plugins > Installed Plugins > All in One SEO Pack and check the version number displayed, or check the plugin header in /wp-content/plugins/all-in-one-seo-pack/aioseo.php
    Affected if The version is 4.2.9 or lower (any version up to and including 4.2.9)
  2. Confirm the plugin is active
    Check if All in One SEO Pack is enabled in the Plugins list in WordPress admin
    Affected if The plugin is active and the version is 4.2.9 or lower
  3. Review plugin settings for injected scripts
    Navigate to All in One SEO > General Settings > Advanced and inspect all text fields (especially SEO title, description, and custom fields) for suspicious <script> tags, javascript: URLs, or event handlers like onload/onerror
    Affected if Any settings contain executable JavaScript that was not entered by an administrator
  4. Audit user accounts with Contributor or higher roles
    Go to Users > All Users in WordPress admin and review accounts with Contributor, Author, Editor, or Administrator roles who have access to plugin settings
    Affected if Untrusted or compromised accounts with Contributor-level access exist and the plugin version is 4.2.9 or lower

You are affected if the All in One SEO Pack plugin version is 4.2.9 or lower AND the plugin is active, regardless of whether malicious scripts have already been injected.

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 4.2.9
Interim mitigation

Update the All in One SEO Pack plugin to a version newer than 4.2.9. Until the update is applied, limit the Contributor role permissions and review existing plugin configurations for injected malicious scripts.

Recommended fix Moderate confidence

The fixed version is any release higher than 4.2.9 - check the WordPress plugin repository for the latest stable release

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'All In One SEO' plugin
  4. 4. Check the current version number (if it shows 4.2.9 or lower, the site is vulnerable)
  5. 5. If an update is available, click 'Update Now' to install the latest version which includes the fix for this vulnerability
Caveat Review the plugin's changelog before upgrading to check for any breaking changes or feature modifications

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

Fix this in All In One Seo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0586 — 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-0586 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