LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38104: WordPress Accordions plugin <= 2.0.3 - Auth. WordPress Options Change vulnerability

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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites running the Accordions or FAQs Builder plugin version 2.0.3 or earlier. An authenticated high-privilege user could change sensitive WordPress settings such as site URL, registration behavior, default role, and administrator email. That can disrupt operations or weaken account controls.

Executive priority

Treat as a high-priority WordPress governance issue for sites using the affected plugin. The risk is not confirmed as actively exploited, but successful abuse could alter core site behavior and account administration settings.

Technical view

CVE-2022-38104 is an authenticated WordPress options change vulnerability in Biplob Adhikari's Accordions plugin <= 2.0.3. The CVSS 3.1 score is 7.2 with network access, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress installations with the Accordions - Multiple Accordions or FAQs Builder plugin at version 2.0.3 or earlier. The provided data does not identify affected CPEs, fixed versions, install counts, or hosted-service exposure.

Exploitation context

The CVE is not marked as CISA KEV, and the provided sources do not state active exploitation. The privilege requirement is high, so this is most concerning where administrator accounts are shared, compromised, or weakly governed.

Researcher notes

The source bundle supports affected product, versions <= 2.0.3, CVSS 7.2, CWE-264, and affected WordPress options. It does not provide proof-of-concept details, exploitation-in-the-wild evidence, or a clearly named fixed version.

Mitigation direction

  • Inventory WordPress sites for the accordions-or-faqs plugin version 2.0.3 or earlier.
  • Check the WordPress plugin page and Patchstack for current vendor guidance or a fixed release.
  • Disable or remove the plugin where no supported safe version is available.
  • Restrict WordPress administrator access and remove stale privileged accounts.
  • Review sensitive WordPress options for unexpected changes.

Validation and detection

  • Confirm plugin presence and version across all WordPress environments.
  • Review siteurl, users_can_register, default_role, admin_email, and new_admin_email values.
  • Audit recent privileged WordPress account activity around configuration changes.
  • Check whether current plugin vendor guidance names a fixed version.
  • Verify backups can restore WordPress options if tampering occurred.
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-38104 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-38104Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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 – Multiple Accordions or FAQs Builder (WordPress plugin)<= 2.0.3Listed
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.