cve.bz

CVE-2026-49049 ollyo helix3: Improper Access Control

7.5 highEPSS 1.0%

High (7.5) in ollyo helix3. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
The Helix3 plugin for Joomla exposes an ajax handler task, that allows unauthenticated attackers to delete arbitrary files, write arbitrary JSON files and update template parameters.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 63rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-06-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-49049 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49049?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49049?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49049 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ollyo:helix3from 1.0 through 3.1.1

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • shinthink/CVE-2026-49049 Harbor Check: matches CVE 4 stars, Python, created
    Read-only vulnerability scanner for CVE-2026-49049 — Helix3 Joomla plugin unauthenticated AJAX handler
  • theendofabbys/CVE-2026-49049 Harbor Check: matches CVE 0 stars, Python, created
  • MataKucing-OFC/CVE-2026-49049 Harbor Check: matches CVE 0 stars, Python, created
  • Jenderal92/CVE-2026-49049 Harbor Check: matches CVE 0 stars, Python, created
    Mass vulnerability scanner for CVE-2026-49049 – Unauthenticated Remote Code Execution in Joomla Helix3 plugin. Multi‑threaded, detects both…
  • 6ickzone/Helix3-Mass-Exploiter Harbor Check: matches CVE 0 stars, created
    Mass Exploiter for CVE-2026-49049
2 more
  • ExDev994/CVE-2026-49049 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2026-49049 Helix3 (JoomShaper) Joomla Unauthenticated AJAX RCE Scanner
  • Dr-D25/CVE-2026-49049 Harbor Check: matches CVE 0 stars, Shell, created

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON