CVE-2022-33198

Accordions – Multiple Accordions or FAQs Builder <= 2.0.2 - Unauthenticated Arbitrary Options Update

2022-06-30 00:00
R3N0

Strategic Overview

Status
Patched in 2.0.3
Affected Plugin
Accordion – Multiple Accordion or FAQs Builder
Affected Version
<= 2.0.2
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-33198
View all Accordion – Multiple Accordion or FAQs Builder vulnerabilities

At a glance

CVE-2022-33198 is a critical-severity Missing Authorization vulnerability in the Accordion WordPress plugin, affecting versions <= 2.0.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed June 2022, reported by R3N0.

Vulnerability Overview

The Accordions plugin for WordPress is vulnerable to arbitrary options update in versions up to, and including, 2.0.2. This is due to insufficient capability checking and option validation. This makes it possible for unauthenticated attackers to modify arbitrary options on the site and can be used for complete site takeover.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in Accordion <= 2.0.2 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Accordion the fix is 2.0.3: builds <= 2.0.2 are affected, anything from 2.0.3 onward is not.

Remediation

Update to version 2.0.3, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Accordion 2.0.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-33198https://www.wordfence.com/threat-intel/vulnerabilities/id/e7a6dee6-b3ff-4325-a356-4a65ab7a0ce5https://nvd.nist.gov/vuln/detail/CVE-2022-33198

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C