CVE-2026-27180Public exploitNetwork attack vector

Unauthenticated code execution via update URL poisoning

Published Feb 18, 2026 · Updated Feb 18, 2026

Remote code execution in SJLab MajorDoMo allows remote attackers to deploy arbitrary PHP files through the saverestore update path. The unauthenticated module handlers accept a requester-supplied update URL, then autoUpdateSystem fetches its feed and tarball without integrity or TLS verification before extraction and copyTree writes every extracted file into the document root. Network access to the web interface is sufficient, and a successful two-request chain places executable webshell content in the webroot.

CVSS severity9.3
Critical
EPSS probability1.09%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Remote code execution in SJLab MajorDoMo allows remote attackers to deploy arbitrary PHP files through the saverestore update path. The unauthenticated module handlers accept a requester-supplied update URL, then autoUpdateSystem fetches its feed and tarball without integrity or TLS verification before extraction and copyTree writes every extracted file into the document root. Network access to the web interface is sufficient, and a successful two-request chain places executable webshell content in the webroot.

The record

CVE
CVE-2026-27180
Published
Feb 18, 2026
Updated
Feb 18, 2026
Vendor
MajorDoMo
Product
MajorDoMo
Classifications
CWE-494, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=*

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

MajorDoMo · MajorDoMoversion=0 <=*

Published CVSS scores

9.3VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-494Download of Code Without Integrity Check
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo