VulnerabilityPublished 21 Feb 2026Updated 24 Feb 2026

CVE-2026-2860: feng_ha_ha ssm-erp · Improper Authorization

Affects feng_ha_ha ssm-erpSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
feng_ha_hassm-erp	Affected =4288d53bd35757b27f2d070057aefb2c07bdd097	Fixed in–
feng_ha_haproduction_ssm	Affected =4288d53bd35757b27f2d070057aefb2c07bdd097	Fixed in–
megagaossm-erp	Affected =4288d53bd35757b27f2d070057aefb2c07bdd097	Fixed in–
megagaoproduction_ssm	Affected =4288d53bd35757b27f2d070057aefb2c07bdd097	Fixed in–

AI-suggested

Implement strict network segmentation to isolate the ssm-erp system from untrusted networks and limit remote access only to trusted administrators or internal users.
Employ application-layer firewalls or web application firewalls (WAFs) to detect and block unauthorized access attempts targeting the EmployeeController endpoints.
Conduct thorough access control reviews and harden authorization logic in custom ERP modules or integrations to prevent privilege escalation.
Monitor logs and network traffic for anomalous access patterns or unauthorized API calls related to employee data or ERP functions.
Use multi-factor authentication and strong identity management for all ERP users to reduce risk from compromised credentials.
Engage with the vendor or community to obtain updates or patches as soon as they become available, and test them promptly.
If possible, implement temporary compensating controls such as disabling or restricting access to vulnerable functions until a patch is released.
Educate IT and security teams about the vulnerability and ensure incident response plans include this threat scenario.
Regularly back up ERP data and verify restoration procedures to mitigate impact of potential data manipulation or destruction.

Description

A security vulnerability has been detected in feng_ha_ha/megagao ssm-erp and production_ssm up to 4288d53bd35757b27f2d070057aefb2c07bdd097. Impacted is an unknown function of the file EmployeeController.java. The manipulation leads to improper authorization. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. This product is distributed under two entirely different names. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The improper authorization vulnerability in ssm-erp can lead to unauthorized access to sensitive employee and organizational data, potentially resulting in data leakage, unauthorized data modification, or disruption of business processes. Since the vulnerability can be exploited remotely without authentication or user interaction, attackers can leverage it to gain elevated privileges or access restricted functions, undermining the integrity and confidentiality of the ERP system. This can facilitate insider-like attacks, data exfiltration, or sabotage of critical business workflows. The rolling release nature of the product complicates patch management, increasing exposure time. Organizations relying on this ERP for human resources, payroll, or operational management may face compliance violations, reputational damage, and operational disruptions. The public availability of exploit code raises the risk of widespread attacks, especially targeting organizations that have not implemented adequate compensating controls or network segmentation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 12:45 UTC

Technical details

References

Community reviews

Related threats