CVE-2022-3691

DeepL Pro API Translation <= 1.7.4 - Sensitive Information Disclosure

2022-10-31 00:00

Strategic Overview

Status: Patched in 1.7.5
Affected Plugin: Translation with DeepL API
Affected Version: <= 1.7.4
CVSS: 6.5Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2022-3691

View all Translation with DeepL API vulnerabilities

At a glance

CVE-2022-3691 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Translation with DeepL API WordPress plugin, affecting versions <= 1.7.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7.5; sites on affected versions should update now. Disclosed October 2022, reported by Raad Haddad.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Translation with DeepL API <= 1.7.4 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Translation with DeepL API the fix is 1.7.5: builds <= 1.7.4 are affected, anything from 1.7.5 onward is not.

Remediation

Update to version 1.7.5, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Translation with DeepL API 1.7.5 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3691 https://www.wordfence.com/threat-intel/vulnerabilities/id/06f3c08a-9791-4c66-a173-8bbbb38d05ab https://nvd.nist.gov/vuln/detail/CVE-2022-3691

Related records

Other vulnerabilities in Translation with DeepL API

CVSS Vector

6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/