CVE-2025-10722VulnerabilityPublished 19 Sep 2025

CVE-2025-10722: SKTLab Mukbee App · Improper Export of Android Application Components

Affects SKTLab Mukbee AppSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

4.8Medium

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

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

CVSS:4.0/AV:L/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: Local
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: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
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 19 Sep 2025
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

Affected software

Product	Affected	Fixed in
SKTLab Mukbee App	Affected =1.01.196	Fixed in–

AI-suggested

Organizations should first assess whether the SKTLab Mukbee App is deployed within their environment and identify affected devices running version 1.01.196. Employ mobile device management (MDM) solutions to monitor app installations and restrict installation of vulnerable app versions. If possible, remove or replace the Mukbee App with a secure alternative until a patched version is released. Educate users about the risks of installing untrusted apps and the importance of securing their devices. Additionally, monitor for any suspicious local activity that could indicate exploitation attempts. Developers or security teams with access to the app codebase should review the AndroidManifest.xml to ensure that exported components are explicitly protected with appropriate permissions or set to not be exported unless necessary. If feasible, implement runtime checks to restrict access to sensitive components. Finally, maintain communication with the vendor for updates or patches and consider reporting the lack of response to relevant security authorities or app marketplaces.

Description

A vulnerability was detected in SKTLab Mukbee App 1.01.196 on Android. This affects an unknown function of the file AndroidManifest.xml of the component com.dw.android.mukbee. The manipulation results in improper export of android application components. The attack must be initiated from a local position. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact depends largely on the usage of the SKTLab Mukbee App within their environment. If the app is used in corporate or sensitive contexts, this vulnerability could allow an attacker with local access to the device to exploit the exposed components to gain unauthorized access to app functions or data, potentially leading to data leakage or privilege escalation on the device. This could compromise confidentiality and integrity of information handled by the app. Since the attack requires local access, the threat is more relevant in scenarios where devices are shared, lost, or physically accessed by unauthorized personnel. In sectors with strict data protection regulations like GDPR, any data leakage or unauthorized access could lead to compliance issues and reputational damage. The lack of vendor response and patch availability increases risk for organizations relying on this app, as they cannot remediate the vulnerability through official updates. However, the medium severity and local attack vector limit the scope of impact primarily to environments where the app is actively used and devices are at risk of local compromise.

Summary

CVE-2025-10722 is a medium-severity vulnerability affecting the SKTLab Mukbee App version 1.01.196 on Android devices. The vulnerability arises from improper exportation of Android application components declared in the AndroidManifest.xml file, specifically within the component com.dw.android.mukbee. Improper export means that certain app components (such as activities, services, or broadcast receivers) are made accessible to other apps or processes without adequate access controls. This can allow a local attacker—someone with physical or logical access to the device—to interact with these components in unintended ways. The vulnerability does not require user interaction but does require the attacker to have at least limited privileges on the device (local access with low privileges). The CVSS 4.0 vector indicates low attack complexity and low privileges required, with no user interaction needed. The impact on confidentiality, integrity, and availability is low, but the vulnerability could be leveraged to escalate privileges, access sensitive data, or manipulate app behavior. The vendor was notified but has not responded or issued a patch, and a public exploit is available, increasing the risk of exploitation. However, there are no known exploits in the wild at this time. This vulnerability is specific to a single app version and does not affect the Android OS itself or other apps. The root cause is a misconfiguration in the AndroidManifest.xml that exposes internal components to other apps or processes without proper protection, which is a common security oversight in Android app development.

References

Community reviews

Loading reviews…