CVE-2022-1037

EXMAGE – WordPress Image Links <= 1.0.6 - Admin+ Blind SSRF

2022-04-14 00:00

Strategic Overview

Status: Patched in 1.0.7
Affected Plugin: EXMAGE – WordPress Image Links
Affected Version: <= 1.0.6
CVSS: 7.2High
Weakness type: CWE-918 · Server-Side Request Forgery (SSRF)
CVE: CVE-2022-1037

View all EXMAGE – WordPress Image Links vulnerabilities

At a glance

CVE-2022-1037 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the EXMAGE WordPress plugin, affecting versions <= 1.0.6. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.0.7; sites on affected versions should update now. Disclosed April 2022, reported by Luan Pedersini.

Vulnerability Overview

The EXMAGE WordPress plugin before 1.0.7 does to ensure that images added via URLs are external images, which could lead to a blind SSRF issue by using local URLs

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in EXMAGE <= 1.0.6 takes a caller who can reach the endpoint. 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. For EXMAGE the fix is 1.0.7: builds <= 1.0.6 are affected, anything from 1.0.7 onward is not.

Remediation

Update to version 1.0.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to EXMAGE: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: EXMAGE 1.0.7 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-1037 https://www.wordfence.com/threat-intel/vulnerabilities/id/0dd1ded1-8966-4247-ab75-17980f00f9b9 https://nvd.nist.gov/vuln/detail/CVE-2022-1037

CVSS Vector

7.2

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

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/