<?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>Realtyna - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/realtyna/</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>Fri, 31 Jul 2026 07:36:25 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/realtyna/feed.xml" rel="self" type="application/rss+xml"/><item><title>Arbitrary File Upload Vulnerability in Realtyna Organic IDX Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-07-realtyna-idx-upload/</link><pubDate>Fri, 31 Jul 2026 07:36:25 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-realtyna-idx-upload/</guid><description>The Realtyna Organic IDX plugin for WordPress contains an arbitrary file upload vulnerability (CVE-2026-16236) due to improper validation and authentication, allowing remote attackers to achieve remote code execution.</description><content:encoded><![CDATA[<p>The Realtyna Organic IDX plugin for WordPress, in versions up to and including 5.3.0, is susceptible to an arbitrary file upload vulnerability. This vulnerability originates from the saveLiveImages() function, which fails to implement necessary file extension and content validation. Additionally, the plugin exhibits insufficient authorization checks within the get_keys() AJAX handler and a complete lack of authentication checks on the REST API import endpoint.</p>
<p>These security flaws permit an authenticated attacker, holding at least subscriber-level privileges, to upload malicious files to the server. By bypassing these checks, an attacker can upload web shells or other malicious scripts, which can then be executed to gain remote code execution (RCE) on the underlying WordPress server. This poses a significant risk to the integrity and confidentiality of the host environment, as it effectively provides a pathway for unauthorized code execution within the web context.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker registers or gains access to a subscriber-level account on a WordPress site utilizing Organic IDX &lt;= 5.3.0.</li>
<li>Attacker targets the insecure REST API import endpoint or the get_keys() AJAX handler to initiate an interaction.</li>
<li>Attacker crafts a malicious payload, such as a PHP web shell, encapsulated within a file upload request.</li>
<li>Attacker sends an HTTP POST request to the vulnerable endpoint, bypassing the insufficient authentication controls.</li>
<li>The saveLiveImages() function fails to validate the file extension or content, allowing the server to save the malicious file to the web root.</li>
<li>Attacker navigates to the uploaded file path via a browser or script to trigger the execution of the embedded code.</li>
<li>The server executes the malicious script under the context of the web server user.</li>
<li>Attacker gains persistence or performs further post-exploitation activities such as data exfiltration.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an authenticated attacker to upload arbitrary files, leading to potential remote code execution. This can result in a full site compromise, sensitive data theft, and the ability to pivot into the underlying server network. All WordPress sites running the Organic IDX plugin version 5.3.0 or earlier are currently at risk.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately update the Realtyna Organic IDX plugin to the latest version that patches CVE-2026-16236.</li>
<li>Disable the Realtyna Organic IDX plugin until a security update is applied if patching cannot be performed immediately.</li>
<li>Audit web server logs for suspicious POST requests targeting /wp-json/ or specific AJAX handler endpoints that result in file creation in public directories.</li>
<li>Restrict access to the WordPress dashboard and administrative REST API endpoints to known, trusted IP addresses to prevent unauthorized access by potential attackers.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Unauthenticated Remote Code Execution in Realtyna Organic IDX and WPL Real Estate WordPress Plugins</title><link>https://feed.craftedsignal.io/briefs/2026-07-realtyna-rce/</link><pubDate>Fri, 31 Jul 2026 07:36:11 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-realtyna-rce/</guid><description>The Realtyna Organic IDX and WPL Real Estate plugins contain an arbitrary file upload vulnerability (CVE-2026-14483) allowing unauthenticated remote code execution via static, default API credentials.</description><content:encoded><![CDATA[<p>The Realtyna Organic IDX and WPL Real Estate plugins for WordPress (versions 5.2.0 and below) contain a critical security vulnerability, tracked as CVE-2026-14483, which allows for unauthenticated remote code execution (RCE). The vulnerability stems from an insecure implementation of the plugin's I/O service endpoint. This endpoint is exposed to the public WordPress init hook without requiring standard WordPress user capability checks.</p>
<p>Authentication for this endpoint relies on static API credentials (api_key and api_secret) that are hardcoded into the plugin's SQL migration files and are identical across every installation. Because these credentials are publicly known, an unauthenticated attacker can successfully authenticate to the I/O service. Once authenticated, the attacker can leverage an insufficiently validated file upload function to drop arbitrary files - including web shells - onto the server. Given the nature of WordPress environments, this permits the attacker to achieve full remote code execution on the underlying host, posing a severe risk to site integrity and data confidentiality.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker performs reconnaissance to identify WordPress sites running vulnerable versions of the Organic IDX or WPL Real Estate plugins.</li>
<li>Attacker probes the web application for the publicly known Realtyna I/O service endpoint.</li>
<li>Attacker crafts an HTTP POST request to the I/O endpoint, embedding the default static api_key and api_secret in the request parameters.</li>
<li>The plugin's authentication logic validates the hardcoded credentials and grants the attacker an authorized session context.</li>
<li>Attacker executes a file upload action via the authorized endpoint, bypassing file type validation controls.</li>
<li>Attacker writes a malicious executable script (e.g., a PHP web shell) into a publicly accessible directory on the WordPress web server.</li>
<li>Attacker sends a secondary HTTP request to the uploaded file to trigger execution.</li>
<li>Attacker gains persistent remote code execution on the WordPress server for further exploitation or exfiltration.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an unauthenticated attacker to take full control of the affected WordPress instance. This includes the ability to modify or delete site content, intercept user data, access the underlying database, and pivot into the internal network environment. This vulnerability affects all installations of the Organic IDX and WPL Real Estate plugins using version 5.2.0 or earlier.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the Organic IDX and WPL Real Estate plugins to the latest version immediately to patch CVE-2026-14483.</li>
<li>Implement the provided Sigma rule to detect suspicious POST requests targeting the I/O service endpoint with known default credential parameters.</li>
<li>Audit the web server filesystem for unauthorized PHP or executable files uploaded within the last 30 days, specifically targeting plugin-related upload directories.</li>
<li>If immediate patching is not possible, restrict access to the I/O endpoint via Web Application Firewall (WAF) rules that block requests containing the known static API keys.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>wordpress</category><category>rce</category><category>file-upload</category><category>cve-2026-14483</category></item></channel></rss>