External Media without Import <= 1.1.2 - Authenticated (Subscriber+) Blind Server-Side Request Forgery
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- External Media without Import
- Affected Version
<= 1.1.2- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2022-1398
At a glance
CVE-2022-1398 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the External Media without Import WordPress plugin, affecting versions <= 1.1.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2022, reported by Luan Pedersini.
Vulnerability Overview
The External Media without Import WordPress plugin through 1.1.2 does not have any authorisation and does to ensure that medias added via URLs are external medias, which could allow any authenticated users, such as subscriber to perform blind SSRF attacks
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 interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in External Media without Import <= 1.1.2 takes an account at Subscriber level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this plugin is recorded for External Media without Import yet, so installs running <= 1.1.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in External Media without Import
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C