LinkedIn Mobile App 4.1.1087.2 on Android Link Preview image/title/description ui wrong action
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in LinkedIn Mobile App 4.1.1087.2 on Android. It has been rated as problematic. This impacts an unknown function of the component Link Preview Handler. This manipulation of the argument image/title/description causes ui wrong action. This vulnerability is handled as CVE-2025-56139. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in LinkedIn Mobile App 4.1.1087.2 on Android. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Link Preview Handler. The manipulation of the argument image/title/description with an unknown input leads to a ui wrong action vulnerability. The CWE definition for the vulnerability is CWE-449. The UI performs the wrong action with respect to the user's request. As an impact it is known to affect integrity. The summary by CVE is:
LinkedIn Mobile Application for Android version 4.1.1087.2 fails to update link preview metadata (image, title, description) when a user replaces the original URL in a post or comment before publishing. As a result, the stale preview remains visible while the clickable link points to a different URL, which can be malicious. This UI misrepresentation enables attackers to deceive users by displaying trusted previews for harmful links, facilitating phishing attacks and user confusion.
The advisory is shared at hdhrmi.blogspot.com. This vulnerability is known as CVE-2025-56139 since 08/16/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/03/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Ui wrong actionCWE: CWE-449
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/16/2025 CVE reserved09/03/2025 Advisory disclosed
09/03/2025 VulDB entry created
09/03/2025 VulDB entry last update
Sources
Advisory: hdhrmi.blogspot.comStatus: Not defined
CVE: CVE-2025-56139 (🔒)
GCVE (CVE): GCVE-0-2025-56139
GCVE (VulDB): GCVE-100-322441
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 09/03/2025 23:38Changes: 09/03/2025 23:38 (55)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.