VulnerabilityPublished 12 Jan 2026

CVE-2026-22788: SMEWebify WebErpMesv2 · Missing Authentication

Affects SMEWebify WebErpMesv2Source CVE Database V5

Not known to be exploited · CVSS 8.2 High : upgrade to 1.19 soon.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score

8.2High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% 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:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 26 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.
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

The primary mitigation is to upgrade WebErpMesv2 installations to version 1.19 or later, where authentication middleware properly protects all sensitive API endpoints. Until upgrading is possible, organizations should implement network-level access controls such as IP whitelisting or VPN restrictions to limit exposure of the vulnerable API endpoints to trusted users only. Conduct a thorough audit of API endpoint accessibility and ensure no sensitive endpoints are publicly reachable without authentication. Employ web application firewalls (WAFs) with rules to detect and block unauthorized API access attempts. Monitor logs for unusual access patterns or unauthorized data retrieval and manipulation activities. Educate internal teams about the vulnerability and encourage vigilance for suspicious behavior. Additionally, review and tighten permissions and roles within the application to minimize potential damage from any unauthorized access. Finally, prepare incident response plans to quickly address any exploitation attempts.

Description

CVE-2026-22788 is a high-severity vulnerability in SMEWebify's WebErpMesv2 versions prior to 1.19, where multiple sensitive API endpoints lack authentication. This allows unauthenticated remote attackers to access critical business data such as companies, quotes, orders, tasks, and whiteboards. Attackers can also perform limited write operations, including creating company records and fully manipulating collaboration whiteboards. The vulnerability does not require user interaction or authentication and has a CVSS score of 8.2, indicating a significant risk to confidentiality and partial impact on integrity. The issue is resolved in version 1.19. European organizations using affected versions face risks of data exposure and unauthorized data manipulation, especially in manufacturing and resource management sectors. Mitigation involves immediate upgrading to version 1.

Impact

For European organizations, especially those in manufacturing and industrial sectors relying on WebErpMesv2 for resource and execution management, this vulnerability presents a substantial risk. Unauthorized access to sensitive business data such as company records, quotes, and orders can lead to intellectual property theft, competitive disadvantage, and regulatory compliance violations under GDPR due to exposure of potentially personal or sensitive data. The ability to manipulate collaboration whiteboards and create company records can disrupt internal workflows, cause misinformation, and potentially lead to financial losses or operational delays. Since the vulnerability requires no authentication and no user interaction, it can be exploited remotely by any attacker scanning for vulnerable endpoints, increasing the attack surface. The lack of availability impact means systems remain operational but compromised in confidentiality and integrity, which can be harder to detect and mitigate. This threat could also facilitate further attacks such as social engineering or supply chain manipulation if attackers leverage the exposed data. The overall impact is high, necessitating urgent remediation to protect business continuity and data privacy.

CWE-306Missing Authentication for Critical Function (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (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:02 UTC

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats