VulnerabilityPublished 29 Aug 2025

CVE-2025-9671: UAB Paytend App · Improper Export of Android Application Components

Affects UAB Paytend AppSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 11:42 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 29 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
UAB Paytend App	Affected 2.1.0 – 2.1.9 10 affected builds	Fixed in–

AI-suggested

Given the lack of an official patch, European organizations should implement several practical mitigations: 1) Restrict physical and local access to devices running vulnerable versions of Paytend through strong device management policies and endpoint security controls. 2) Employ Mobile Device Management (MDM) solutions to enforce app usage policies, restrict installation of unauthorized apps, and monitor for suspicious local activity. 3) Encourage users to update to newer versions of Paytend if and when patches become available; meanwhile, consider alternative payment apps with better security posture. 4) Conduct regular security audits and penetration testing focusing on local privilege escalation and app component exposure. 5) Use Android security features such as app sandboxing, permission management, and disabling debugging options to reduce attack surface. 6) Educate users about risks of local attacks and the importance of device security. 7) Monitor for any emerging exploit activity related to this CVE and be prepared to respond swiftly.

Description

A weakness has been identified in UAB Paytend App up to 2.1.9 on Android. This impacts an unknown function of the file AndroidManifest.xml of the component com.passport.cash. Executing manipulation can lead to improper export of android application components. The attack needs to be launched locally. 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, especially those relying on UAB Paytend for payment processing or financial transactions, this vulnerability could lead to unauthorized local access to sensitive financial information or manipulation of app behavior. While remote exploitation is not possible, insider threats or attackers with physical access to devices could leverage this flaw to compromise confidentiality and integrity of payment data. This could result in financial fraud, data breaches, or loss of customer trust. Organizations in sectors such as banking, retail, or any service using Paytend for payments should be particularly cautious. The lack of vendor response and absence of patches increases the risk exposure. Additionally, the vulnerability could be exploited in corporate environments where employees use Paytend on company-issued Android devices, potentially leading to lateral movement or privilege escalation within internal networks.

Summary

CVE-2025-9671 is a medium-severity vulnerability affecting the UAB Paytend Android application versions 2.1.0 through 2.1.9. The vulnerability arises from improper export of Android application components declared in the AndroidManifest.xml file, specifically related to the component com.passport.cash. 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 local access to the device—to manipulate these components, potentially leading to unauthorized access or actions within the app context. The attack vector requires local access and does not require user interaction, but does require at least limited privileges (PR:L). The CVSS 4.0 vector indicates low attack complexity and partial impact on confidentiality, integrity, and availability. Although the exploit code has been publicly released, there are no known exploits in the wild yet. This vulnerability is significant because financial or payment apps like Paytend often handle sensitive user data and transactions, so improper component exposure could lead to data leakage or unauthorized transaction manipulation if exploited.

References

Community reviews

Loading reviews…