Skip to content
Fencer Intel
critical 9.8

CVE-2023-4634 in the critical feed json

Media Library Assistant <= 3.09 - Unauthenticated Local/Remote File Inclusion & Remote Code Execution

published 3y ago modified 5mo ago also EUVD-2023-54487

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
85.6%
EPSS 85.6% chance of exploitation in 30 days, percentile 99.7%
public exploits
1
Exploit-DB

Summary

The Media Library Assistant plugin for WordPress is vulnerable to Local File Inclusion and Remote Code Execution in versions up to, and including, 3.09. This is due to insufficient controls on file paths being supplied to the 'mla_stream_file' parameter from the ~/includes/mla-stream-image.php file, where images are processed via Imagick(). This makes it possible for unauthenticated attackers to supply files via FTP that will make directory lists, local file inclusion, and remote code execution possible.

Patch / fix

  • davidlingren media_library_assistant 3.10

Is CVE-2023-4634 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-51737)

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

85.60% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-22).

Exploits and checks

  • EDB-51737 Media Library Assistant Wordpress Plugin - RCE and LFI webapps, 2023-10-09
  • patrowl.io https://patrowl.io/blog-wordpress-media-library-rce-cve-2023-4634/ referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/Patrowl/CVE-2023-4634/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • dglingren Media Library Assistant

Classification

Weakness
  • CWE-73 External Control of File Name or Path
Technology feeds

References

Sources

Fencer Intel 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.