VulnerabilityPublished 10 Jan 2023Updated 30 May 2025

CVE-2022-38482: Mega HOPEX · Link Following

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

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

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

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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).
Availability: None: There is no impact to availability within the impacted component.
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: None: There is no loss of integrity within the impacted 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.
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.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jan 2023
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 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

AI-suggested

European organizations using Mega HOPEX should prioritize updating to version V5CP4 or later, as this is the only known remediation step. In the absence of direct patch links, contacting the vendor for official updates and guidance is critical. Additionally, organizations should implement strict user training to recognize and avoid suspicious links, especially those received via email or messaging platforms. Deploying email filtering and anti-phishing solutions can reduce the likelihood of malicious link delivery. Network segmentation and strict access controls should be enforced to limit the exposure of the Mega HOPEX environment. Monitoring and logging user interactions with the application can help detect anomalous behavior indicative of exploitation attempts. Finally, conducting regular security assessments and penetration tests focusing on link handling and file access controls within Mega HOPEX can identify residual risks.

Description

A link-manipulation issue was discovered in Mega HOPEX 15.2.0.6110 before V5CP4.

Impact

For European organizations, the impact of CVE-2022-38482 centers on potential confidentiality breaches within enterprise architecture and business process management data. Since Mega HOPEX is used to model and analyze critical business processes, unauthorized access to this information could lead to exposure of sensitive corporate strategies, internal workflows, or personal data, potentially violating GDPR requirements. Although the vulnerability does not affect system integrity or availability, the confidentiality loss could facilitate further targeted attacks or corporate espionage. The requirement for user interaction means phishing or social engineering campaigns could be vectors for exploitation. Organizations relying on Mega HOPEX for compliance, risk management, or strategic planning could face reputational damage and regulatory penalties if confidential data is leaked. The medium CVSS score reflects a moderate risk, but the sensitivity of the data involved elevates the importance of addressing this vulnerability promptly.

CWE-59Improper Link Resolution Before File Access ('Link Following') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Symlink Attack (opens in a new tab)
Using Malicious Files (opens in a new tab)
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating Web Input to File System Calls (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

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:55 UTC

WeaknessesCWE-59

Technical details

References

Community reviews

Related threats