CVE-2026-1356
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-1356 is a Server-Side Request Forgery (SSRF) vulnerability in the "Converter for Media – Optimize images | Convert WebP & AVIF" plugin for WordPress. It affects all versions up to and including 6.5.1, allowing unauthenticated attackers to make arbitrary web requests originating from the web server. The vulnerability was published on February 12, 2026, with a CVSS v3.1 base score of 4.8 (Medium) (Red Hat CVE, Feedly).

Technical details

The root cause is improper validation of user-supplied input within the PassthruLoader::load_image_source function, classified as CWE-918 (Server-Side Request Forgery). An unauthenticated attacker can craft a request that causes the plugin to fetch an arbitrary URL from the server side, enabling interaction with internal services not directly accessible from the internet. Exploitation requires high attack complexity (AC:H) but no privileges or user interaction, meaning a skilled attacker can trigger the SSRF without any authentication (Red Hat CVE, Feedly).

Impact

Successful exploitation allows unauthenticated attackers to query and potentially modify information from internal services reachable by the web server, including internal APIs, databases, and cloud metadata endpoints (e.g., AWS IMDSv1). The confidentiality and integrity impacts are rated Low, with no direct availability impact, but access to cloud metadata services could facilitate privilege escalation or lateral movement within cloud-hosted environments (Red Hat CVE, Feedly).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.029%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. A Nuclei detection template pull request was submitted to the ProjectDiscovery repository, suggesting community interest in automated scanning (Feedly, Nuclei Templates PR).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the "Converter for Media" plugin (versions ≤ 6.5.1) using tools like WPScan, Shodan, or by inspecting plugin directories at /wp-content/plugins/converter-for-media/.
  2. Craft SSRF payload: Construct an HTTP request targeting the vulnerable PassthruLoader::load_image_source function, supplying an attacker-controlled URL (e.g., http://169.254.169.254/latest/meta-data/ for AWS metadata, or an internal service address) as the image source parameter.
  3. Send unauthenticated request: Submit the crafted request to the WordPress site without any authentication credentials, triggering the plugin to fetch the specified URL from the server.
  4. Retrieve response: Observe the server's response or use out-of-band techniques (e.g., a controlled external server) to capture data returned from the internal service, enabling enumeration of internal infrastructure or extraction of sensitive metadata (Red Hat CVE, Feedly).

Indicators of compromise

  • Network: Outbound HTTP/HTTPS requests from the web server to internal IP ranges (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or cloud metadata endpoints (169.254.169.254); unexpected DNS lookups for internal hostnames originating from the WordPress server.
  • Logs: Web server access logs showing requests to WordPress endpoints associated with the Converter for Media plugin containing unusual or internal URLs as parameter values; repeated requests with varying internal IP targets suggesting enumeration.
  • File System: No specific file artifacts expected for SSRF exploitation, but review for any newly created files if SSRF is chained with other vulnerabilities.
  • Process: Unusual outbound connections initiated by the PHP/web server process to non-standard destinations, detectable via network monitoring tools or host-based firewalls.

Mitigation and workarounds

The vendor has released a patch in version 6.5.2 of the Converter for Media plugin; all users running version 6.5.1 or earlier should upgrade immediately via the WordPress plugin dashboard. If immediate patching is not feasible, temporarily deactivating the plugin is recommended to eliminate the attack surface. Additionally, implement network-level controls to restrict the web server's outbound access to internal services, and monitor outbound connections for anomalous activity (Red Hat CVE, Feedly).

Community reactions

Sucuri included CVE-2026-1356 in their February 2026 vulnerability patch roundup, highlighting it as one of several WordPress plugin issues requiring attention (Sucuri Blog). Spanish national cybersecurity agencies INCIBE-CERT and CCN-CERT also published alerts for the vulnerability, indicating broader European awareness (INCIBE-CERT, CCN-CERT). Community interest is reflected in a Nuclei template pull request for automated detection (Nuclei Templates PR).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management