How severe is CVE-2022-1037?

CVE-2022-1037 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-1037 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-1037?

CVE-2022-1037 affects Villatheme Exmage. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-1037?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-1037 published?

CVE-2022-1037 was published on 2022-04-18 and last updated on 2026-06-17.

CVE-2022-1037

CVE-2022-1037 is a high-severity vulnerability in Villatheme Exmage with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-918.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v2: 6.5
EPSS exploit prediction: 1% (70th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-918
Affected product: Villatheme Exmage
Published: 2022-04-18
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2022-1037?: 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
How severe is CVE-2022-1037?: CVE-2022-1037 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-1037 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-1037?: CVE-2022-1037 affects Villatheme Exmage. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-1037?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-1037 published?: CVE-2022-1037 was published on 2022-04-18 and last updated on 2026-06-17.

References

https://wpscan.com/vulnerability/bd8555bd-8086-41d0-a1f7-3557bc3af957

Affected products (1)

cpe:2.3:a:villatheme:exmage:*:*:*:*:*:wordpress:*:*

Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities

CVE-2026-54734 — Critical (CVSS 10.0): Prebid Server Java is the Java version of Prebid Server. Prior to 3.43.0, certain bidder adapters interpolate…
CVE-2026-76193 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in…
CVE-2026-69502 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Azure SQL Database allows an unauthorized attacker to elevate privileges over a…
CVE-2026-65801 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Microsoft Exchange Online allows an unauthorized attacker to elevate privileges…
CVE-2026-48331 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in…
CVE-2026-54735 — Critical (CVSS 10.0): Prebid Server is an open-source solution for running real-time advertising auctions in the cloud. Prior to version…

Browse all CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities →