LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45071: WordPress WPML Multilingual CMS premium plugin <= 4.5.13 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin <= 4.5.13 on WordPress.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using WPML Multilingual CMS premium plugin versions 4.5.13 and earlier. It is a CSRF issue: an attacker could trick a logged-in user into triggering unintended plugin actions. The recorded impact is limited integrity and availability, with no confidentiality impact in the supplied CVSS data.

Executive priority

Treat this as a moderate remediation item for WordPress estates using WPML. It is not shown as actively exploited in the provided sources, but it can affect site integrity or availability if an authenticated user is tricked into an unintended action.

Technical view

CVE-2022-45071 is CWE-352 CSRF in OnTheGoSystems WPML Multilingual CMS for WordPress, affecting versions up to 4.5.13. CVSS 3.1 is 5.4: network attack vector, low complexity, no privileges required by the attacker, user interaction required, and limited integrity and availability impact.

Likely exposure

Exposure is limited to WordPress installations running the premium WPML Multilingual CMS plugin at version 4.5.13 or earlier. Sites not using this plugin, or running versions outside the affected range, are not shown as affected by the supplied sources.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. CSRF normally depends on tricking a legitimate user into interacting with attacker-controlled content while authenticated, so real risk is higher for administrative users who are logged into WordPress.

Researcher notes

The supplied data identifies the vulnerable product and version range, CWE, CVSS vector, and Patchstack reference, but does not provide affected endpoint details, exploit proof, or a named fixed version. Avoid assuming specific plugin actions until vendor advisory details are reviewed.

Mitigation direction

  • Inventory WordPress sites for WPML Multilingual CMS plugin usage and version.
  • Prioritize sites running WPML Multilingual CMS 4.5.13 or earlier.
  • Check WPML or Patchstack guidance for the fixed version and update path.
  • Reduce administrator exposure to untrusted links while remediation is pending.
  • Review WordPress security controls that limit unintended authenticated actions.

Validation and detection

  • Confirm installed WPML Multilingual CMS version on each WordPress site.
  • Verify whether any installation is version 4.5.13 or earlier.
  • Check vendor or Patchstack advisory details for current remediation status.
  • After updating, recheck plugin version and affected-site inventory.
  • Review logs for unusual administrative changes around sensitive plugin settings.
Prepared
Confidence
medium
Sources
3

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-45071 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
2Source 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-45071Attack 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
OnTheGoSystems Ltd.WPML Multilingual CMS (WordPress plugin)<= 4.5.13Listed
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.