
Advisory and proof-of-concept details for CVE-2026-49049, an unauthenticated arbitrary JSON file write in the Joomla Helix3 plugin, with exploitation steps, patch and mitigation guidance.
Affected versions: Helix3 1.0 through 3.1.1. Fixed in 3.1.2 .
Vulnerability type: CWE-284, Improper Access Control. CVSS v3.1 = 7.5 (HIGH). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N .
Root cause: The onAjaxHelix3() handler in the plg_ajax_helix3 plugin is reachable through Joomla's built-in com_ajax component at POST /index.php?option=com_ajax&plugin=helix3&format=json. The handler processes data[action]=save requests with no authentication check, no CSRF token validation, and no path traversal filtering on the data[layoutName] parameter. The value is concatenated directly onto the layout directory path before fopen() and fwrite() are called .
Exploitation: An unauthenticated attacker sends a single POST with data[action]=save&data[layoutName]=../../../attacker-file&data[content]={"probe":"test"}. Three levels of traversal from the default template layout directory land in the Joomla web root. The handler creates attacker-file.json in the web root, immediately accessible over HTTP. The same handler also exposes data[action]=remove for arbitrary .json file deletion and data[action]=import for template configuration overwrite .
Active exploitation: Observed in the wild as part of the AntonKill botnet defacement campaign . Listed on the CISA Known Exploited Vulnerabilities catalog . EPSS score varies by source (0.00992 to 0.23) .
Fix: Upgrade Helix3 to 3.1.2 or later. The patch enforces administrator privileges (core.admin/core.manage on com_templates) and valid CSRF tokens for all admin AJAX actions, adds a deny-by-default allowlist, sanitizes layout filenames to alphanumeric/hyphen/underscore only, and uses realpath() to block directory traversal .
Interim mitigation if patching is delayed: Block POST requests to index.php where the query string contains both option=com_ajax and plugin=helix3 at the WAF or web server level . Alternatively, disable the plg_ajax_helix3 plugin entirely if front-end AJAX functionality is not required .
Post-patch audit: Updating the plugin does not remove malicious content already written to the database or filesystem. Check the template style's Custom Code fields (Custom JavaScript, Custom CSS, Before </head>, Before </body>) for injected code, and inspect the /images directory for unexpected .php or .json files .