Security readout for executives and security teams
Plain-English summary
CVE-2021-4410 affects the Qtranslate Slug WordPress plugin through version 1.1.18. A malicious party could trick a logged-in site administrator into taking an action that changes post data. This is not a server takeover issue, but it can create unauthorized content changes on affected WordPress sites.
Executive priority
Treat as a moderate website integrity risk. Prioritize remediation for public WordPress sites where content trust, SEO, or publishing workflows matter, but do not rank it like remote code execution or credential theft based on current sources.
Technical view
The flaw is CWE-352 cross-site request forgery caused by missing or incorrect nonce validation in save_postdata(). The CVSS 3.1 score is 4.3, with network attack vector, low complexity, no privileges required, user interaction required, and low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites running Qtranslate Slug up to and including 1.1.18. Risk is most relevant where administrators are logged in while browsing external links or untrusted content.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation depends on tricking a site administrator into performing an action; it is not described as unauthenticated direct compromise.
Researcher notes
Evidence supports a CSRF issue in Qtranslate Slug save_postdata(), affecting integrity only under the stated CVSS vector. The bundle does not provide a precise fixed version or active exploitation evidence, so validation should focus on version and nonce-control review.
Mitigation direction
- Inventory WordPress sites for the Qtranslate Slug plugin and exact version.
- Upgrade or remove vulnerable versions after confirming vendor or Wordfence guidance.
- If no fixed maintained release is available, disable the plugin until risk is accepted.
- Reduce administrator exposure to untrusted links while logged into WordPress.
- Review post-change workflows for unauthorized content edits.
Validation and detection
- Check each WordPress installation for Qtranslate Slug version 1.1.18 or earlier.
- Confirm whether save_postdata() includes valid nonce verification in the installed code.
- Review WordPress admin activity for unexpected post data changes.
- Verify remediation by confirming the vulnerable plugin version is no longer present.
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-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 lookupCVE-2021-4410 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
- Medium
- CVSS
- 4.3 (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:N
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:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9d682596-c32d-4abd-ba39-b57fc45c9ce0?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/browser/qtranslate-slug/trunk/includes/class-qtranslate-slug.php#L2099CVE 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.
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.