CVE-2026-22789VulnerabilityPublished 12 Jan 2026

CVE-2026-22789: SMEWebify WebErpMesv2 · Unrestricted File Upload

Affects SMEWebify WebErpMesv2Source CVE Database V5

Mentioned vulnerabilities

CVE-2025-52130

Not known to be exploited · CVSS 5.4 Medium : upgrade to 1.19 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Upgrade WebErpMesv2 and smewebify/WebErpMesv2 to 1.19.

Affected software

Product	Affected	Fixed in
SMEWebifyWebErpMesv2	Affected <1.19	Fixed in 1.19
GitHubsmewebify/WebErpMesv2`pkg:github/smewebify/WebErpMesv2`Other threats	Affected <1.19	Fixed in 1.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade WebErpMesv2 to version 1.19 or later immediately, as this version contains the official fix for the vulnerability. 2. Enforce strict access control policies to limit authenticated user privileges, ensuring only trusted personnel have upload permissions. 3. Implement multi-factor authentication (MFA) to reduce the risk of credential compromise. 4. Monitor and log all file upload activities, focusing on unusual file types or upload patterns, and establish alerts for suspicious behavior. 5. Employ web application firewalls (WAF) with custom rules to detect and block attempts to upload executable scripts or files with dangerous extensions. 6. Conduct regular security audits and penetration testing focused on file upload functionalities. 7. Educate users on secure credential management and phishing awareness to reduce the risk of account compromise. 8. Isolate the WebErpMesv2 application environment to limit the impact of potential exploitation, such as running it in a container or segmented network zone. 9. Review and harden server configurations to prevent execution of uploaded files in upload directories, for example by disabling script execution in upload folders. 10. Maintain up-to-date backups and incident response plans tailored to manufacturing execution system environments.

Description

CVE-2026-22789 is a medium-severity vulnerability in SMEWebify's WebErpMesv2 versions prior to 1.19 that allows authenticated users to bypass file upload validation and upload arbitrary files, including PHP scripts. This can lead to remote code execution (RCE) on the affected system. The flaw exists in multiple controllers and is similar to CVE-2025-52130 but in different code locations not fixed previously. Exploitation requires authentication but no user interaction beyond that. The vulnerability impacts confidentiality and integrity but not availability, with a CVSS score of 5.4. No known exploits are currently reported in the wild. European organizations using WebErpMesv2 in manufacturing or resource management should prioritize upgrading to version 1.19 or later to mitigate risk.

Impact

For European organizations, especially those in manufacturing, industrial resource management, and supply chain sectors using WebErpMesv2, this vulnerability poses a significant risk. Successful exploitation could allow attackers to execute arbitrary code on critical systems, potentially leading to data breaches, intellectual property theft, sabotage of manufacturing processes, or lateral movement within corporate networks. The confidentiality and integrity of sensitive operational data could be compromised, affecting production quality and business continuity. Given the industrial focus of the product, disruption or manipulation of manufacturing execution systems could have downstream effects on supply chains and operational safety. While availability is not directly impacted by this vulnerability, the consequences of unauthorized code execution could indirectly cause downtime or degraded service. The requirement for authenticated access limits exposure to internal or credential-compromised attackers but does not eliminate risk, especially in environments with weak access controls or phishing susceptibility. European organizations with stringent regulatory requirements around data protection and operational security must address this vulnerability promptly to avoid compliance issues and reputational damage.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-616Incomplete Identification of Uploaded File Variables (PHP) (opens in a new tab)
Variant weakness
The PHP application uses an old method for processing uploaded files by referencing the four global variables that are set for each file (e.g. $varname, $varname_size, $varname_name, $varname_type). These variables could be overwritten by attackers, causing the application to process unauthorized files.
Architecture and Design
Use PHP 4 or later.
Architecture and Design
If you must support older PHP versions, write your own version of is_uploaded_file() and run it against $HTTP_POST_FILES['userfile']))
Implementation
For later PHP versions, reference uploaded files using the $HTTP_POST_FILES or $_FILES variables, and use is_uploaded_file() or move_uploaded_file() to ensure that you are dealing with an uploaded file.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 03:00 UTC

WeaknessesCWE-434, CWE-616

Technical details

References

Community reviews

Related threats