CVE-2025-49590 Vulnerability Analysis & Exploit Details

CVE-2025-49590
Vulnerability Scoring

6.1
/10
High Risk

If left unpatched, CVE-2025-49590 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2025-49590 Details

Status: Analyzed

Last updated: 🕕 11 Aug 2025, 18:18 UTC
Originally published on: 🕚 18 Jun 2025, 23:15 UTC

Time between publication and last update: 53 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2025-49590 Vulnerability Summary

CVE-2025-49590: CryptPad is a collaboration suite. Prior to version 2025.3.0, the "Link Bouncer" functionality attempts to filter javascript URIs to prevent Cross-Site Scripting (XSS), however this can be bypassed. There is an "early allow" code path that happens before the URI's protocol/scheme is checked, which a maliciously crafted URI can follow. This issue has been patched in version 2025.3.0.

Assessing the Risk of CVE-2025-49590

Access Complexity Graph

The exploitability of CVE-2025-49590 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-49590

With low attack complexity and no required privileges, CVE-2025-49590 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-49590, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-49590, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-49590 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2025-49590 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2025-49590 does not impact system availability.

CVE-2025-49590 References

External References

CWE Common Weakness Enumeration

CWE-692

CAPEC Common Attack Pattern Enumeration and Classification

  • Double Encoding CAPEC-120 The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. However, many filters recognize this encoding and would still block the request. In a double encoding, the % in the above URL encoding would be encoded again as %25, resulting in %252E which some filters might not catch, but which could still be interpreted as a dot (.) by interpreters on the target.
  • Leverage Alternate Encoding CAPEC-267 An adversary leverages the possibility to encode potentially harmful input or content used by applications such that the applications are ineffective at validating this encoding standard.
  • Using Unicode Encoding to Bypass Validation Logic CAPEC-71 An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.
  • Using UTF-8 Encoding to Bypass Validation Logic CAPEC-80 This attack is a specific variation on leveraging alternate encodings to bypass validation logic. This attack leverages the possibility to encode potentially harmful input in UTF-8 and submit it to applications not expecting or effective at validating this encoding standard making input filtering difficult. UTF-8 (8-bit UCS/Unicode Transformation Format) is a variable-length character encoding for Unicode. Legal UTF-8 characters are one to four bytes long. However, early version of the UTF-8 specification got some entries wrong (in some cases it permitted overlong characters). UTF-8 encoders are supposed to use the "shortest possible" encoding, but naive decoders may accept encodings that are longer than necessary. According to the RFC 3629, a particularly subtle form of this attack can be carried out against a parser which performs security-critical validity checks against the UTF-8 encoded form of its input, but interprets certain illegal octet sequences as characters.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:a:xwiki:cryptpad:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.20.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.20.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.22.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.22.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.23.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.24.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.26.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.26.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.27.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.27.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.28.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.28.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:1.29.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:1.29.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.17.05:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.17.05:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.17.06:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.17.06:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.20.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.20.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.22.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.22.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.23.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.24.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:2.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:2.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:xwiki:cryptpad:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:xwiki:cryptpad:3.1.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-49590: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-55613 – Tenda O3V2 1.0.0.12(3880) is vulnerable to Buffer Overflow in the fromSafeSetMacFilter function via the mac parameter.
  • CVE-2025-55581 – D-Link DCS-825L firmware version 1.08.01 and possibly prior versions contain an insecure implementation in the mydlink-watch-dog.sh script. The scr...
  • CVE-2025-52287 – OperaMasks SDK ELite Script Engine v0.5.0 was discovered to contain a deserialization vulnerability.
  • CVE-2025-52085 – An SQL injection vulnerability in Yoosee application v6.32.4 allows authenticated users to inject arbitrary SQL queries via a request to a backend ...
  • CVE-2025-43760 – A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.4, 20...