LiveActive security incident?Get immediate response
CVE Record

CVE-2022-33198: WordPress Accordions plugin <= 2.0.2 - Unauthenticated WordPress Options Change vulnerability

Unauthenticated WordPress Options Change vulnerability in Biplob Adhikari's Accordions plugin <= 2.0.2 at WordPress.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical WordPress plugin issue affecting Accordions <= 2.0.2. An unauthenticated attacker could change WordPress options, which can undermine site integrity, confidentiality, and availability. Sites using this plugin should treat exposure as urgent until the plugin is removed, disabled, or confirmed remediated through vendor guidance.

Executive priority

Prioritize remediation for any public WordPress site using Accordions <= 2.0.2. The vulnerability is remotely reachable, unauthenticated, and rated critical. Business risk is highest where WordPress supports lead generation, customer trust, payments, or public brand presence.

Technical view

CVE-2022-33198 is an unauthenticated WordPress options change vulnerability in Biplob Adhikari's Accordions plugin for WordPress, affecting versions <= 2.0.2. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required. The supplied CWE is CWE-264.

Likely exposure

Exposure is limited to WordPress sites with the Accordions plugin installed at version 2.0.2 or earlier. The bundle does not identify specific hosting platforms, configurations, CPEs, or affected forks. Public internet-facing WordPress sites would carry the highest business risk.

Exploitation context

The source bundle marks this CVE as not in KEV and provides no cited evidence of active exploitation. The CVSS vector indicates unauthenticated remote attack potential. Because the issue involves WordPress options, compromise impact could be broad, but exact exploit mechanics are not provided.

Researcher notes

Evidence is sufficient for affected product, affected version range, severity, and vulnerability class. It is not sufficient to name a fixed version, root cause, exploit path, or active exploitation. Avoid live exploit validation; use version checks, configuration review, and vendor advisory tracking.

Mitigation direction

  • Inventory WordPress sites for the Accordions plugin and installed version.
  • Disable or remove Accordions <= 2.0.2 until vendor guidance confirms remediation.
  • Check Patchstack and the WordPress plugin page for vendor-confirmed fixed versions.
  • Review recent backups before making recovery or rollback decisions.
  • Monitor WordPress option changes and unexpected site configuration drift.

Validation and detection

  • Confirm whether Accordions is installed on each WordPress site.
  • Record the exact plugin version and compare it with the <= 2.0.2 affected range.
  • Review WordPress options for unexpected administrative or site URL changes.
  • Check web and application logs for suspicious unauthenticated plugin-related activity.
  • Verify the plugin is removed, disabled, or updated per vendor guidance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-264: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-33198 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-33198Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Biplob AdhikariAccordions (WordPress plugin)<= 2.0.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-264 · source CWE mapping

Permissions, Privileges, and Access Controls

Permissions, Privileges, and Access Controls represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.