Security readout for executives and security teams
Plain-English summary
This is a WordPress plugin issue where a logged-in user's browser could be abused into sending an unintended request. The documented impact is limited to low integrity change, not data theft or downtime. It matters only where the Fluenx DeepL API translation plugin is installed in an affected version.
Executive priority
Treat as a moderate WordPress plugin hygiene item. It is not documented as actively exploited and has low integrity impact, but internet-facing WordPress estates should still identify and remediate affected plugin installations promptly.
Technical view
The CVE records a CWE-352 CSRF vulnerability in Fluenx DeepL API translation plugin, reported for versions up to 2.3.9.1. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites running the Fluenx DeepL API translation plugin, package wpdeepl, in the affected version range. The provided sources do not identify affected configurations beyond the plugin and version data.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. The CVSS vector requires user interaction, consistent with CSRF risk. No exploit details are provided, and none should be inferred.
Researcher notes
Evidence is limited to CVE and Patchstack-style vulnerability records. The bundle states affected versions are <=2.3.9.1, while the Patchstack URL slug references 2.3.6.6, so validate exact affected and fixed versions against current vendor guidance before closure.
Mitigation direction
- Inventory WordPress sites for the wpdeepl or DeepL API translation plugin.
- Compare installed versions against the affected range in CVE and Patchstack records.
- Check vendor or Patchstack guidance for a fixed version or official workaround.
- Prioritize removal or disablement where the plugin is unused.
- Require normal admin anti-phishing controls while remediation is pending.
Validation and detection
- Confirm whether each WordPress instance has the plugin installed.
- Record the exact installed plugin version from WordPress administration or asset inventory.
- Verify whether a vendor-fixed release is available before upgrading.
- Check change management records for plugin disablement or update completion.
- Review logs only for unusual admin actions; sources do not confirm exploitation.
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-2023-46620 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
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.