Security readout for executives and security teams
Plain-English summary
Betheme for WordPress had a high-risk flaw allowing any authenticated subscriber-level user to submit unsafe serialized data. If a suitable object chain exists in the site’s code, that could lead to code execution, data theft, or file deletion. Evidence does not show CISA KEV listing or active exploitation.
Executive priority
Treat as high priority for public WordPress properties using Betheme. The required privilege is low, so sites with customer, community, or open registration accounts should be reviewed first. Prioritize inventory, update guidance, and account exposure reduction.
Technical view
CVE-2022-3861 is CWE-502 PHP object injection in Betheme up to 26.5.1.4. Untrusted input reaches deserialization through builder import-related parameters and functions. The CVSS 3.1 score is 8.8, requiring network access and low privileges, with high confidentiality, integrity, and availability impact.
Likely exposure
Internet-facing WordPress sites running Betheme version 26.5.1.4 or earlier are the primary exposure, especially where untrusted users can authenticate as subscribers. The source bundle’s affected-version metadata is incomplete, so validate against vendor and Wordfence records.
Exploitation context
The vulnerability requires an authenticated user with subscriber-level permissions or higher. The source bundle states severe outcomes require an additional POP chain. No provided source confirms active exploitation, and the CVE is not marked as KEV.
Researcher notes
Focus review on unsafe deserialization in builder import paths named by the CVE: import, mfn-items-import-page, and mfn-items-import flowing through related import functions. Impact depends on available gadget or POP chains, so site-specific plugin and theme composition matters.
Mitigation direction
- Identify all WordPress sites using MuffinGroup Betheme.
- Update Betheme according to MuffinGroup and Wordfence guidance.
- Remove unnecessary subscriber or higher-privilege accounts.
- Disable open user registration where business use does not require it.
- Review vendor advisories before assuming a specific fixed version.
Validation and detection
- Check installed Betheme versions against 26.5.1.4 or earlier.
- Confirm whether untrusted users can authenticate to affected sites.
- Review logs for unusual builder import activity by low-privilege users.
- Verify remediation by confirming the updated theme version.
- Document any exposed sites requiring compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupCVE-2022-3861 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f5e984d5-2537-4a4a-a071-084e0c1c3b5e?source=cveCVE reference
- https://muffingroup.com/betheme/CVE reference
- https://github.com/MrTuxracer/advisories/blob/master/CVEs/CVE-2022-3861.txtCVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-3861CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
