Deepl Pro Api TranslationWordPress extension · Fluenx
CVE-2023-27446
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.1.4 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 affecting versions 2.1.4 and below. The vulnerability allows attackers to induce authenticated users to perform unintended actions through malicious requests, potentially manipulating translation configurations or API usage.
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 Pro Api TranslationWordPress extension
<= 2.1.4CVSS 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.
-
Verify the Fluenx Deepl plugin is installedCheck your WordPress plugins directory or the Plugins admin page to confirm the Fluenx Deepl Pro Api Translation plugin is present and activeAffected if The plugin is installed and active in WordPress
-
Identify the installed versionLocate the main plugin file and read the version header comment, or check the version displayed in the WordPress plugin admin interfaceAffected if The installed version is 2.1.4 or any version lower (e.g., 2.1.3, 2.1.2, 2.0.0)
-
Inspect form submissions for nonce validationExamine the plugin source code for nonce fields in forms and verify wp_nonce_field or wp_nonce_url functions are used on all state-changing operations (settings updates, configuration changes)Affected if Forms handling translation settings lack nonce validation or token checks
-
Check AJAX requests for nonce verificationReview any AJAX handlers in the plugin and confirm that check_ajax_referer or wp_verify_nonce is called before processing requestsAffected if AJAX endpoints processing configuration changes do not verify nonces
-
Verify Referer or SameSite cookie protectionsLook for server-side Referer header validation or SameSite attribute settings on session cookies used by the pluginAffected if No Referer validation or SameSite cookie flags are implemented for authenticated requests
Your environment is affected if the Fluenx Deepl Pro Api Translation plugin version is 2.1.4 or lower AND the plugin lacks anti-CSRF protections (nonce validation, Referer checks, or SameSite cookies) on its configuration-changing operations.
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 dataImplement anti-CSRF tokens or checks (such as checking the Referer header or using SameSite cookies) on all state-changing operations within the plugin. Ensure proper nonce validation is applied to all form submissions and AJAX requests.
Fix this in Deepl Pro Api Translation
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27446 — 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-27446 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