CVE-2025-52580VulnerabilityPublished 22 Jul 2025

CVE-2025-52580: Gift Pad "region PAY" App for Android · Sensitive Data in Logs

Affects Gift Pad "region PAY" App for AndroidSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low : upgrade to 1.5.28 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

2.4Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.5.28

CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable 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.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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.
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.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jul 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 2026-10-25.

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

Upgrade Gift Pad "region PAY" App for Android to 1.5.28.

Affected software

Product	Affected	Fixed in
Gift Pad Co.,Ltd. "region PAY" App for Android	Affected <1.5.28	Fixed in 1.5.28

AI-suggested

1. Immediate update to version 1.5.28 or later of the "region PAY" app once available, as this version addresses the logging issue. 2. Implement device-level security controls such as full-disk encryption, strong authentication, and remote wipe capabilities to reduce the risk of unauthorized access to application logs. 3. Educate users on the risks of installing untrusted applications or granting excessive permissions that could expose app logs. 4. For organizations deploying the app, enforce mobile device management (MDM) policies that restrict access to application data and logs. 5. Monitor for unusual access patterns or malware that could access app logs on devices. 6. Encourage developers to adopt secure logging practices, such as avoiding logging sensitive data and using secure storage mechanisms for sensitive information. 7. Conduct regular security audits and penetration testing on mobile applications to detect similar issues proactively.

Description

Insertion of sensitive information into log file issue exists in "region PAY" App for Android prior to 1.5.28. If exploited, sensitive user information may be exposed to an attacker who has access to the application logs.

Impact

For European organizations, especially those involved in financial services or mobile payments, this vulnerability could lead to unauthorized disclosure of sensitive user data if devices running vulnerable versions of the "region PAY" app are compromised. Although the vulnerability requires access to application logs, which limits remote exploitation, the risk remains significant in environments where devices may be lost, stolen, or infected with malware that can access app logs. Exposure of sensitive payment or personal information could lead to privacy violations, regulatory non-compliance (e.g., GDPR), reputational damage, and potential financial fraud. Organizations using or recommending the "region PAY" app should be aware of this risk, particularly in sectors with high regulatory scrutiny or where mobile payment adoption is high. The vulnerability does not affect system integrity or availability, so operational disruption is unlikely; however, confidentiality breaches could have legal and customer trust implications.

References

jvn.jp/en/jp/JVN07825095/ (opens in a new tab)

Community reviews

Loading reviews…