dbcve.org
AccordionsWordPress extension · Oxilab

CVE-2022-33198

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-21
Fix available
A fix is available. Upgrade to 2.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Unauthenticated WordPress Options Change vulnerability in Biplob Adhikari's Accordions plugin <= 2.0.2 at 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 · moderate confidence

Unauthenticated attackers can modify WordPress options settings through the Accordions plugin version 2.0.2 or earlier. This options change vulnerability allows modification of WordPress site settings without authentication, potentially affecting site configuration, user registration, or other core settings.

MitigationUpdate the Accordions plugin to a version newer than 2.0.2 immediately. Review and restore any unauthorized WordPress options changes that may have occurred.

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.0.3

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Accordions plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Accordions' or 'Oxilab Accordions' in the list. Note whether it is installed and active.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed plugin version
    In the Plugins list, click on the plugin name to view details, or check the plugin's main PHP file header for the Version field. Compare the version number to the affected range.
    Affected if The installed version is 2.0.2 or earlier (any version below 2.0.3).
  3. Inspect plugin options handling
    Check the plugin files (typically in wp-content/plugins/accordions or similar) for AJAX handlers or options-update functions that lack capability checks or nonce verification, particularly in files handling WordPress options.
    Affected if The plugin contains code that allows modification of WordPress options (add_option, update_option, etc.) without requiring authentication or proper authorization checks.
  4. Review WordPress site options for unauthorized changes
    In WordPress admin, go to Settings > General, Settings > Reading, and other settings pages. Check for unexpected values in siteurl, home, users_can_register, default_role, or other core options.
    Affected if Core WordPress options have been modified to values you did not intentionally set, indicating potential exploitation.

You are affected if the Oxilab Accordions plugin version 2.0.2 or earlier is installed and active on your WordPress site, allowing unauthenticated attackers to modify WordPress options settings.

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.0.3 or later
Fixed in 2.0.3
Interim mitigation

Update the Accordions plugin to a version newer than 2.0.2 immediately. Review and restore any unauthorized WordPress options changes that may have occurred.

Recommended fix High confidence

Accordions plugin version 2.0.3

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Accordions' plugin by Biplob Adhikari
  4. Click 'Update now' if an update is available, or manually update to version 2.0.3
  5. After updating, verify the plugin is running version 2.0.3 or higher
  6. Review WordPress options/settings that may have been changed by attackers (check for new admin accounts, modified site URLs, etc.)

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

Fix this in Accordions Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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