LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36798: WordPress Mega Addons For WPBakery Page Builder plugin <= 4.2.7 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Topdigitaltrends Mega Addons For WPBakery Page Builder plugin <= 4.2.7 at WordPress.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress Mega Addons For WPBakery Page Builder plugin through version 4.2.7. An attacker could trick a user’s browser into causing limited unwanted changes or disruption on an affected site. The sources do not show active exploitation.

Executive priority

Treat this as a moderate WordPress hygiene issue. It is not presented as actively exploited, but affected public sites should be identified and remediated because CSRF can create unauthorized changes through trusted user sessions.

Technical view

CVE-2022-36798 is CWE-352 in Topdigitaltrends Mega Addons For WPBakery Page Builder for WordPress, affecting versions <= 4.2.7. CVSS 3.1 is 5.4, network-accessible, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites that have the Mega Addons For WPBakery Page Builder plugin installed at version 4.2.7 or earlier.

Exploitation context

The provided data marks this as not in KEV and gives no cited evidence of exploitation in the wild. The CVSS vector indicates a remote attacker would need user interaction, consistent with CSRF risk against an active browser session.

Researcher notes

Evidence is sparse: the bundle identifies the affected plugin, version boundary, CWE, CVSS, and references, but does not provide endpoint details, proof-of-concept status, or a named fixed version. Avoid assuming impact beyond low integrity and availability.

Mitigation direction

  • Inventory WordPress sites for this plugin and record installed versions.
  • Check WordPress.org, Patchstack, and vendor guidance for a fixed release or mitigation.
  • Update the plugin if vendor guidance identifies a remediated version.
  • Disable or remove the plugin if it remains at <= 4.2.7 and no fix is available.
  • Review administrative accounts and recent site changes for unexpected activity.

Validation and detection

  • Confirm whether the plugin slug mega-addons-for-visual-composer is installed.
  • Verify the installed plugin version is not <= 4.2.7.
  • Review change logs or vendor advisories for the remediation status.
  • Check WordPress audit logs for unusual administrative actions around user-reported clicks.
  • Document affected sites, remediation decisions, and remaining exceptions.
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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-36798 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-36798Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
TopdigitaltrendsMega Addons For WPBakery Page Builder (WordPress plugin)<= 4.2.7Listed
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.