dbcve.org
AccordionsWordPress extension · Oxilab

CVE-2022-38104

HIGH · 7.2 CVSS v3.1 Published 2022-10-21
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Auth. WordPress Options Change (siteurl, users_can_register, default_role, admin_email and new_admin_email) vulnerability in Biplob Adhikari's Accordions – Multiple Accordions or FAQs Builder plugin (versions <= 2.0.3 on WordPress.

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

An authenticated attacker with subscriber-level access or higher can modify critical WordPress options (siteurl, users_can_register, default_role, admin_email, new_admin_email) through the Accordions plugin. This allows redirecting the site to a malicious URL, enabling user registration with attacker-controlled roles, or changing the admin email to hijack administrator accounts.

MitigationUpgrade the Accordions plugin to version 2.0.4 or later. If immediate upgrade is not possible, disable the plugin until the update can be applied.

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
AccordionsWordPress extension
Affected:< 2.1.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Identify if Accordions plugin is installed
    Check your WordPress wp-content/plugins directory for the 'accordions' folder, or view the installed plugins list in WP Admin under Plugins > Installed Plugins
    Affected if The 'accordions' plugin folder exists in wp-content/plugins
  2. Check the installed version of Accordions
    In WP Admin, go to Plugins > Installed Plugins and look for 'Accordions' or 'Oxilab Accordions' to find the version number. Alternatively, check the main plugin PHP file header in wp-content/plugins/accordions/ for 'Version:' field
    Affected if The version listed is below 2.1.0 (such as 2.0.x or earlier)
  3. Verify the plugin is active
    In WP Admin > Plugins > Installed Plugins, confirm the Accordions plugin shows as 'Active'
    Affected if Accordions is currently activated on the site
  4. Check for low-privilege user accounts
    In WP Admin > Users, review the list of users and their assigned roles. Check if any users have 'Subscriber' role or if user registration is enabled allowing new subscriber registrations
    Affected if There are subscriber-level accounts OR the 'Anyone can register' setting is enabled with Subscriber as the default role
  5. Check critical WordPress options for unauthorized changes
    In WP Admin > Settings > General, verify that 'Site URL' matches your expected domain, 'New Admin Email' is not set to an unfamiliar address, and 'Membership' shows 'Anyone can register' is unchecked unless intended
    Affected if Siteurl differs from expected value, admin_email or new_admin_email points to an unknown address, or users_can_register is enabled with a high-risk default_role

A user is affected if the Accordions plugin version is below 2.1.0, the plugin is active, AND an attacker could obtain or already has subscriber-level access to the WordPress site.

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 2.1.0 or later
Fixed in 2.1.0
Interim mitigation

Upgrade the Accordions plugin to version 2.0.4 or later. If immediate upgrade is not possible, disable the plugin until the update can be applied.

Recommended fix High confidence

Accordions plugin version 2.1.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Accordions – Multiple Accordions or FAQs Builder' plugin
  4. Click 'Update now' if an update is available, or manually upload version 2.1.0 or later
  5. Verify the update completed successfully
  6. Test that the plugin functionality works as expected

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

Fix this in Accordions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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