Lever PDF Embedder Plugin 4.4 on WordPress PDF Document interpretation conflict

Summaryinfo

A vulnerability, which was classified as critical, has been found in Lever PDF Embedder Plugin 4.4 on WordPress. This affects an unknown function. The manipulation as part of PDF Document leads to input validation. This vulnerability is listed as CVE-2019-19589. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Lever PDF Embedder Plugin 4.4 on WordPress (WordPress Plugin). This issue affects an unknown functionality. The manipulation as part of a PDF Document leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-436. Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The Lever PDF Embedder plugin 4.4 for WordPress does not block the distribution of polyglot PDF documents that are valid JAR archives. Note: It has been argued that "The vulnerability reported in PDF Embedder Plugin is not valid as the plugin itself doesn't control or manage the file upload process. It only serves the uploaded PDF files and the responsibility of uploading PDF file remains with the Site owner of Wordpress installation, the upload of PDF file is managed by Wordpress core and not by PDF Embedder Plugin. Control & block of polyglot file is required to be taken care at the time of upload, not on showing the file. Moreover, the reference mentions retrieving the files from the browser cache and manually renaming it to jar for executing the file. That refers to a two step non-connected steps which has nothing to do with PDF Embedder.

The weakness was presented 12/05/2019. The identification of this vulnerability is CVE-2019-19589 since 12/05/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/05/2024).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Name

• Lever PDF Embedder Plugin

Version

• 4.4

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion