WpmlWordPress extension
CVE-2022-45071
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin <= 4.5.13 on WordPress.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin versions 4.5.13 and below allows attackers to trick authenticated administrators into performing unintended actions, such as modifying plugin settings or site configuration, by exploiting the lack of proper nonce validation on sensitive WordPress admin actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
WpmlWordPress extension
< 4.5.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate WPML plugin installationCheck the WordPress plugins directory for the WPML Multilingual CMS plugin files, typically found in /wp-content/plugins/sitepress-multilingual-cms/, or check via WordPress admin dashboard under Plugins > Installed PluginsAffected if WPML plugin is present in the WordPress installation
-
Identify installed WPML versionView the plugin header or main file (usually sitepress-multilingual-cms.php) to read the Version comment, or check the WordPress admin plugins list which displays version numbers next to each pluginAffected if The installed version is less than 4.5.14
-
Verify plugin is activeCheck WordPress admin dashboard under Plugins > Installed Plugins to confirm WPML status; CSRF requires an authenticated administrator session to be exploitableAffected if WPML is activated on the site
If the installed WPML version is 4.5.13 or below and the plugin is active, the environment is affected by this CSRF vulnerability due to missing nonce validation on admin actions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.5.14
Implement WordPress nonces (wp_nonce_field/check_admin_referer) on all state-changing admin actions and forms within the plugin; upgrade to version 4.6.0 or later which contains the security fix.
WPML Multilingual CMS 4.5.14 or later
- Log in to your WordPress admin dashboard
- Navigate to the WPML plugin settings or plugins page
- Update WPML Multilingual CMS to version 4.5.14 or later
- Verify the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wpml
Scoped from the published advisory
- Consultation3.0 h
- Implementation12.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45071 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data