<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2026-33534 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-33534/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 27 May 2026 13:11:10 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-33534/feed.xml" rel="self" type="application/rss+xml"/><item><title>EspoCRM 9.3.3 SSRF Vulnerability (CVE-2026-33534)</title><link>https://feed.craftedsignal.io/briefs/2026-05-espocrm-ssrf/</link><pubDate>Wed, 27 May 2026 13:11:10 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-espocrm-ssrf/</guid><description>A public exploit is available for EspoCRM 9.3.3, exploiting a Server-Side Request Forgery (SSRF) vulnerability (CVE-2026-33534) allowing authenticated attackers to potentially access internal resources.</description><content:encoded><![CDATA[<p>A Server-Side Request Forgery (SSRF) vulnerability has been identified in EspoCRM version 9.3.3, tracked as CVE-2026-33534. An authenticated attacker can exploit this vulnerability to potentially force the server to make requests to unintended locations, including internal services that are normally protected. The public availability of an exploit (EDB-52583) increases the risk of exploitation. The vulnerability exists in the <code>Attachment/fromImageUrl</code> endpoint which is used to fetch images from a provided URL. Attackers can manipulate the <code>url</code> parameter to point to internal resources by bypassing URL validation through techniques like IP address encoding.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to the EspoCRM application.</li>
<li>Attacker crafts a malicious request to the <code>/api/v1/Attachment/fromImageUrl</code> endpoint.</li>
<li>The request includes a <code>url</code> parameter containing a manipulated IP address (e.g., octal, hex, or decimal representation) pointing to an internal resource.</li>
<li>EspoCRM server, due to insufficient validation, processes the crafted URL.</li>
<li>The server initiates a request to the attacker-specified internal resource.</li>
<li>The server receives a response from the internal resource.</li>
<li>The server may then process or display the received data, potentially leaking sensitive information or enabling further attacks.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SSRF vulnerability (CVE-2026-33534) in EspoCRM 9.3.3 could allow an attacker to access sensitive internal resources, such as internal web applications, databases, or configuration files. This can lead to information disclosure, privilege escalation, or further compromise of the EspoCRM system and the underlying network. The exploit&rsquo;s public availability means organizations using unpatched versions of EspoCRM are at heightened risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the patch or upgrade to a version of EspoCRM that addresses CVE-2026-33534 as outlined in the vendor&rsquo;s advisory (<a href="https://github.com/espocrm/espocrm/security/advisories/GHSA-h7gx-8gwv-7g73">https://github.com/espocrm/espocrm/security/advisories/GHSA-h7gx-8gwv-7g73</a>).</li>
<li>Implement input validation and sanitization on the <code>url</code> parameter of the <code>/api/v1/Attachment/fromImageUrl</code> endpoint to prevent SSRF attacks.</li>
<li>Deploy the Sigma rule <code>Detect EspoCRM SSRF via Encoded Loopback</code> to identify exploitation attempts targeting CVE-2026-33534.</li>
<li>Monitor web server logs for requests to the <code>/api/v1/Attachment/fromImageUrl</code> endpoint containing unusual or encoded IP addresses in the <code>url</code> parameter.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>ssrf</category><category>webapps</category><category>cve-2026-33534</category></item></channel></rss>