CVE-2025-41408VulnerabilityPublished 5 Sep 2025

CVE-2025-41408: LY "Yahoo! Shopping" App for Android · Improper authorization in handler for custom URL scheme

Affects LY "Yahoo! Shopping" App for AndroidSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 14.15.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

4.3Medium

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.
Patch: Available – fixed in 14.15.0

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: 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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of confidentiality within the impacted component.
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 on 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 5 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 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 LY "Yahoo! Shopping" App for Android to 14.15.0.

Affected software

Product	Affected	Fixed in
LY Corporation "Yahoo! Shopping" App for Android	Affected <14.15.0	Fixed in 14.15.0

AI-suggested

1. Immediate mitigation involves educating users about the risks of clicking unsolicited or suspicious links, especially those purporting to open the Yahoo! Shopping app or related services. 2. Organizations should enforce mobile device management (MDM) policies that restrict installation of outdated app versions and encourage timely updates. 3. Monitor for phishing campaigns targeting users of the Yahoo! Shopping app and implement email and web filtering solutions to block malicious URLs. 4. Encourage users to update the Yahoo! Shopping app to version 14.15.0 or later as soon as the patch is available to ensure the vulnerability is remediated. 5. Developers and security teams should audit custom URL scheme handlers in mobile apps to ensure proper authorization and validation of input URLs to prevent similar vulnerabilities. 6. Implement multi-factor authentication (MFA) on critical services to reduce the impact of credential theft resulting from phishing. 7. Consider deploying endpoint protection solutions capable of detecting phishing attempts and malicious URL redirections on mobile devices.

Description

Improper authorization in handler for custom URL scheme issue in "Yahoo! Shopping" App for Android versions prior to 14.15.0 allows a remote unauthenticated attacker may lead a user to access an arbitrary website on the vulnerable App. As a result, the user may become a victim of a phishing attack.

Impact

For European organizations, the primary risk posed by this vulnerability is the facilitation of phishing attacks targeting employees or customers using the Yahoo! Shopping Android app. While the vulnerability does not directly compromise device confidentiality or availability, successful exploitation can lead to credential theft, unauthorized access to corporate accounts, or fraud if users are tricked into entering sensitive information on attacker-controlled websites. Retailers, e-commerce platforms, and financial institutions in Europe may face indirect impacts if their customers are targeted via this vector, potentially damaging brand reputation and customer trust. Additionally, organizations with BYOD (Bring Your Own Device) policies or that rely on mobile commerce apps should be aware of the increased phishing risk. The vulnerability’s exploitation requires user interaction, which somewhat limits its impact scope, but the widespread use of the Yahoo! Shopping app in certain European markets could increase exposure. Since the vulnerability affects only Android devices, organizations with a significant Android user base are more at risk. The lack of known exploits in the wild reduces immediate threat urgency but does not eliminate the risk of future exploitation.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Sep 2025, 13:55 UTC

Technical details

References

Community reviews

Related threats