VulnerabilityPublished 27 Dec 2025Updated 29 Dec 2025

CVE-2025-15106: getmaxun maxun · Improper Authorization

Affects getmaxun maxunSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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 27 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 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

Affected software

Product	Affected	Fixed in
npmmaxun`pkg:npm/maxun`Other threats	Affected 0.0.1 – 0.0.28 <=0.0.28 28 affected builds	Fixed in–

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

AI-suggested

Since no official patches or updates are available, European organizations should implement immediate compensating controls. These include restricting network access to the vulnerable authentication endpoint via firewalls or network segmentation to limit exposure to trusted sources only. Conduct thorough code reviews and audits of authentication logic to identify and remediate improper authorization checks. Deploy enhanced monitoring and alerting on authentication endpoints to detect anomalous or unauthorized access attempts. Consider temporary disabling or replacing the vulnerable maxun component if feasible. Engage in threat hunting to identify any signs of exploitation within the environment. Maintain up-to-date backups and incident response plans in case of compromise. Finally, monitor vendor channels for any forthcoming patches or advisories and plan prompt deployment once available.

Description

A weakness has been identified in getmaxun maxun up to 0.0.28. The affected element is the function router.get of the file server/src/routes/auth.ts of the component Authentication Endpoint. Executing manipulation can lead to improper authorization. The attack can be executed remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the improper authorization vulnerability in maxun could lead to unauthorized access to sensitive systems or data, undermining confidentiality and integrity. Attackers could exploit this flaw to escalate privileges or access restricted resources, potentially disrupting business operations or leaking sensitive information. Organizations using maxun in critical authentication workflows or identity management systems face increased risk of compromise. The absence of vendor response and patches prolongs exposure, increasing the likelihood of exploitation attempts. This could affect sectors with stringent data protection requirements such as finance, healthcare, and government. Additionally, the vulnerability could be leveraged as a foothold for further lateral movement within networks. The medium severity suggests moderate impact, but the ease of exploitation and public availability of exploits elevate the threat level for European entities relying on this software.

Summary

CVE-2025-15106 identifies an improper authorization vulnerability in the maxun product, specifically in the router.get function of the Authentication Endpoint implemented in server/src/routes/auth.ts. This flaw allows remote attackers to bypass authorization controls by manipulating requests to this endpoint, potentially gaining unauthorized access or privileges. The vulnerability affects all versions up to 0.0.28, indicating a long-standing issue across many releases. The attack vector is network-based with low complexity, requiring no authentication or user interaction, which facilitates exploitation. The vendor was notified early but has not issued any patches or advisories, and public exploit code is available, increasing the risk of active exploitation. The vulnerability impacts confidentiality, integrity, and availability to a limited extent (low impact on each), resulting in a CVSS 4.0 base score of 5.3 (medium severity). The lack of authentication requirements and the remote nature of the exploit make this a notable threat for systems relying on maxun for authentication services. No mitigations or patches have been published, leaving organizations exposed unless they implement compensating controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 23:44 UTC

Technical details

References

Community reviews

Related threats