VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 3 known issues Latest disclosed Oct 25, 2023

Translation with DeepL API Vulnerabilities

Review known vulnerability records for the WordPress plugin Translation with DeepL API (`wpdeepl`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2023-46620, CVE-2023-27446 and CVE-2022-3691, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
3
High or Critical
0
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing Translation with DeepL API fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Translation with DeepL API remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
3
1. Match the Package
Confirm the installed WordPress plugin slug is wpdeepl before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
3 records include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2022-3691 Medium
Vulnerability remediation for Translation with DeepL API

Affected range: Versions up to 1.7.4. Fixed version: 1.7.5.

CVE-2023-46620 Medium
Cross-Site Request Forgery remediation for Translation with DeepL API

Affected range: Versions up to 2.4.1.1. Fixed version: 2.4.1.2.

CVE-2023-27446 Medium
Cross-Site Request Forgery remediation for Translation with DeepL API

Affected range: Versions up to 2.1.4. Fixed version: 2.1.5.

Priority CVE Quick Links

Fast paths into Translation with DeepL API CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
3
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2022-3691
DeepL Pro API Translation <= 1.7.4 - Sensitive Information Disclosure
 Vulnerability Versions up to 1.7.4 1.7.5 CVSS 6.5
CVE-2023-46620
DeepL Pro API translation <= 2.4.1.1 - Cross-Site Request Forgery via wpdeepl_prune_...
 Cross-Site Request Forgery Versions up to 2.4.1.1 2.4.1.2 CVSS 4.3
CVE-2023-27446
DeepL Pro API translation <= 2.1.4 - Cross-Site Request Forgery via saveSettings
 Cross-Site Request Forgery Versions up to 2.1.4 2.1.5 CVSS 4.3
CVE-2022-3691 Medium 1.7.5
CVE-2022-3691 Translation with DeepL API Vulnerability

DeepL Pro API Translation <= 1.7.4 - Sensitive Information Disclosure

CVE-2023-46620 Medium 2.4.1.2
CVE-2023-46620 Translation with DeepL API Cross-Site Request Forgery

DeepL Pro API translation <= 2.4.1.1 - Cross-Site Request Forgery via wpdeepl_prune_logs

CVE-2023-27446 Medium 2.1.5
CVE-2023-27446 Translation with DeepL API Cross-Site Request Forgery

DeepL Pro API translation <= 2.1.4 - Cross-Site Request Forgery via saveSettings

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Translation with DeepL API so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
3 records include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2023-46620, CVE-2023-27446 and CVE-2022-3691
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Translation with DeepL API

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2023-46620
CVE-2023-46620: DeepL Pro API translation <= 2.4.1.1 - Cross-Site Request Forgery via wpdeepl_prune_logs

The DeepL Pro API translation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4.1.1. This is due to missing or incorrect nonce validation on the wpdeepl_prune_logs function. This makes it possible for unauthenticated attackers...

Published
Oct 25, 2023
Patched Release
2.4.1.2
Affected Versions
Versions up to 2.4.1.1
Next Step
Update to 2.4.1.2 or newer if supported.
Review CVE-2023-46620 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2023-27446
CVE-2023-27446: DeepL Pro API translation <= 2.1.4 - Cross-Site Request Forgery via saveSettings

The DeepL Pro API translation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1.4. This is due to missing or incorrect nonce validation on the 'saveSettings' function. This makes it possible for unauthenticated attackers to cha...

Published
Mar 02, 2023
Patched Release
2.1.5
Affected Versions
Versions up to 2.1.4
Next Step
Update to 2.1.5 or newer if supported.
Review CVE-2023-27446 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2022-3691
CVE-2022-3691: DeepL Pro API Translation <= 1.7.4 - Sensitive Information Disclosure

The DeepL Pro API Translation plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 1.7.4. This could allow unauthenticated attackers to extract sensitive user or configuration data such as API keys.

Published
Oct 31, 2022
Patched Release
1.7.5
Affected Versions
Versions up to 1.7.4
Next Step
Update to 1.7.5 or newer if supported.
Review CVE-2022-3691 fixed version details Open CVE Reference