Deepl Api TranslationWordPress extension · Fluenx
CVE-2023-46620
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 Fluenx DeepL API translation plugin <= 2.3.9.1 versions.
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 the Fluenx DeepL API translation plugin for WordPress versions 2.3.9.1 and below. The flaw allows remote attackers to trick authenticated administrators into submitting unintended requests to the plugin's endpoints, potentially manipulating translation settings or API configurations.
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
Deepl Api TranslationWordPress extension
<= 2.3.9.1CVSS 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.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Fluenx Deepl Api Translation' or check the plugins directory for the deepl-translation folderAffected if The plugin is not found in the WordPress installation
-
Check installed versionIn WordPress admin_plugins page, find the Fluenx DeepL API Translation plugin and read the version number displayed beneath the plugin nameAffected if Version is 2.3.9.1 or lower
-
Verify plugin is activeIn WordPress admin_plugins page, check if the Fluenx Deepl Api Translation plugin shows as 'Active'Affected if Plugin is active (inactive plugins cannot be exploited)
-
Inspect for nonce validation in plugin codeUsing a file manager or code editor, examine the plugin's main PHP file for form handling and AJAX actions. Search for 'wp_nonce_field', 'check_admin_referer', or 'check_ajax_referer' calls on state-changing functionsAffected if No nonce verification is found on forms or AJAX actions that modify settings or API configurations
A user is affected if the Fluenx DeepL API Translation plugin version 2.3.9.1 or lower is installed and active, and the plugin code lacks CSRF token validation on its configuration endpoints
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.
From vendor dataUpdate the Fluenx DeepL API translation plugin to the latest version which includes proper CSRF token validation for state-changing requests, or ensure all plugin forms and AJAX actions implement WordPress nonces.
Fix this in Deepl Api Translation
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46620 — 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-2023-46620 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