CVE-2025-13473 Vulnerability Analysis & Exploit Details

CVE-2025-13473
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2025-13473 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-13473 Details

Status: Analyzed

Last updated: 🕔 04 Feb 2026, 17:10 UTC
Originally published on: 🕒 03 Feb 2026, 15:16 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-13473 Vulnerability Summary

CVE-2025-13473: An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. The `django.contrib.auth.handlers.modwsgi.check_password()` function for authentication via `mod_wsgi` allows remote attackers to enumerate users via a timing attack. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Stackered for reporting this issue.

Assessing the Risk of CVE-2025-13473

Access Complexity Graph

The exploitability of CVE-2025-13473 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-13473

This vulnerability, CVE-2025-13473, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

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-13473, 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-13473, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2025-13473 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2025-13473 poses no threat to data integrity.
  • Availability: None
    CVE-2025-13473 does not impact system availability.

CVE-2025-13473 References

External References

CWE Common Weakness Enumeration

CWE-208

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross-Domain Search Timing CAPEC-462 An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain.
  • Application Fingerprinting CAPEC-541 An adversary engages in fingerprinting activities to determine the type or version of an application installed on a remote target.
  • System Footprinting CAPEC-580 An adversary engages in active probing and exploration activities to determine security information about a remote target system. Often times adversaries will rely on remote applications that can be probed for system configurations.

Vulnerable Configurations

  • cpe:2.3:a:djangoproject:django:4.2:-:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2:-:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2:a1:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2:a1:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2:b1:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2:b1:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.11:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.11:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.12:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.12:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.13:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.13:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.14:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.14:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.15:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.15:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.16:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.16:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.17:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.17:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.18:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.18:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.19:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.19:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.20:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.20:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.21:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.21:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.22:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.22:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.23:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.23:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.24:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.24:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.25:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.25:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:4.2.26:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:4.2.26:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:djangoproject:django:5.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:djangoproject:django:5.2.8:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-13473: 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-2026-2565 – A weakness has been identified in Wavlink WL-NU516U1 20251208. Affected by this issue is the function sub_40785C of the file /cgi-bin/adm.cgi. This...
  • CVE-2026-2564 – A security flaw has been discovered in Intelbras VIP 3260 Z IA 2.840.00IB005.0.T. Affected by this vulnerability is an unknown functionality of the...
  • CVE-2026-2101 – A Reflected Cross-site Scripting (XSS) vulnerability affecting ENOVIAvpm Web Access from ENOVIAvpm Version 1 Release 16 through ENOVIAvpm Version 1...
  • CVE-2026-26930 – SmarterTools SmarterMail before 9526 allows XSS via MAPI requests.
  • CVE-2026-2563 – A vulnerability was identified in JingDong JD Cloud Box AX6600 up to 4.5.1.r4533. Affected is the function set_stcreenen_deabled_status/get_status ...