CVE-2023-3371 json
EmbedPress <= 3.7.3 - Sensitive Information Exposure
published 2023-06-27 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-44038
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
The EmbedPress plugin for WordPress is vulnerable to Sensitive Information Exposure due to hardcoded encryption key on the 'lock_content_form_handler' and 'display_password_form' function in versions up to, and including, 3.7.3. This makes it possible for unauthenticated attackers to decrypt and view the password protected content.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- wpdevteam EmbedPress – PDF Embedder, Embed YouTube Videos, 3D FlipBook, Social feeds, Docs & more
Classification
- Weakness
-
- CWE-321 Use of Hard-coded Cryptographic Key
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2930523/embedpress#file10
patch
-
plugins.trac.wordpress.org
/changeset/2930523/embedpress#file28
patch
-
wordfence.com
/threat-intel/vulnerabilities/id/c1033b4d-82a0-4484-aebf-f35d6a2a9a13?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/embedpress/tags/3.7.3/Gutenberg/block-backend/block-embedpress.php#L30
product
-
plugins.trac.wordpress.org
/browser/embedpress/tags/3.7.3/EmbedPress/Includes/Classes/Helper.php#L231
product
-
plugins.trac.wordpress.org
/browser/embedpress/tags/3.7.3/EmbedPress/Includes/Classes/Helper.php#L278
product
Sources
- CVE List CVE-2023-3371
- NVD CVE-2023-3371
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.