VulnerabilityPublished 19 Aug 2025

CVE-2025-9134: AfterShip Package Tracker App · Improper Export of Android Application Components

Affects AfterShip Package Tracker AppSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

4.8Medium

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.

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 Aug 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
AfterShip Package Tracker App	Affected =5.24.0 =5.24.1	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should take the following specific actions: 1) Immediately audit the usage of the AfterShip Package Tracker App across all managed Android devices and identify those running affected versions (5.24.0 and 5.24.1). 2) Restrict installation of the vulnerable app versions through mobile device management (MDM) solutions until a patch is released. 3) Educate users about the risks of local exploitation and enforce strict device access controls, including strong authentication and device encryption to prevent unauthorized local access. 4) Monitor devices for unusual app behavior or unauthorized access attempts to the AfterShip app components. 5) Once the vendor releases a patch, prioritize prompt deployment of the update across all affected devices. 6) Consider alternative package tracking solutions with better security postures if immediate patching is not feasible. 7) Implement application sandboxing and restrict inter-app communication where possible to limit the impact of improperly exported components.

Description

A security vulnerability has been detected in AfterShip Package Tracker App up to 5.24.1 on Android. The affected element is an unknown function of the file AndroidManifest.xml of the component com.aftership.AfterShip. The manipulation leads to improper export of android application components. The attack must be carried out locally. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure and replied: "After reviewing your report, we have confirmed that this vulnerability does indeed exist and we are actively working to fix it."

Impact

For European organizations, the impact of CVE-2025-9134 depends largely on the usage of the AfterShip Package Tracker App within their environment. Organizations that rely on this app for logistics, supply chain tracking, or package management could face risks related to unauthorized access to app components, potentially leading to leakage of sensitive shipment data or manipulation of tracking information. Although the attack requires local access, insider threats or compromised devices could exploit this vulnerability to gain unauthorized access or disrupt operations. This could affect confidentiality of shipment details, integrity of tracking data, and potentially availability if app components are manipulated to cause malfunction. Given the medium severity and local attack vector, the threat is more relevant to organizations with mobile device management policies that allow installation of third-party apps or where devices are shared or less controlled. The vulnerability also poses a risk to individual users in Europe who use the app, potentially leading to privacy breaches or data exposure.

Summary

CVE-2025-9134 is a security vulnerability identified in the AfterShip Package Tracker App versions up to 5.24.1 on the Android platform. The root cause of this vulnerability lies in the improper export of Android application components, specifically due to misconfigurations in the AndroidManifest.xml file within the component com.aftership.AfterShip. Exported components in Android apps are accessible to other apps or processes on the device, and improper export can lead to unauthorized access or manipulation of app components. In this case, the vulnerability requires local access to the device, meaning an attacker must have some level of access or control over the device to exploit it. The vulnerability does not require user interaction and can be exploited with low complexity, as indicated by the CVSS vector (AV:L/AC:L/PR:L/UI:N). The impact on confidentiality, integrity, and availability is limited but present, as the vulnerability allows for potential unauthorized access or manipulation of app components, which could lead to data leakage or app behavior manipulation. No known exploits are reported in the wild yet, but the vulnerability has been publicly disclosed, increasing the risk of exploitation attempts.

References

Community reviews

Loading reviews…