dbcve.org
WinrarApplication · Rarlab

CVE-2025-52331

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting (XSS) vulnerability in the generate report functionality in Rarlab WinRAR 7.11, allows attackers to disclose user information such as the computer username, generated report directory, and IP address. The generate report command includes archived file names without validation in the HTML report, which allows potentially malicious HTML tags to be injected into the report. User interaction is required. User must use the "generate report" functionality and open the report.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DOM-based XSS vulnerability in WinRAR 7.11's generate report functionality. When generating HTML reports, archived file names are included without sanitization, allowing injection of malicious HTML/script tags. Successful exploitation discloses user information including computer username, report directory path, and IP address to an attacker.

MitigationAwait vendor patch from Rarlab. Users should avoid generating reports from untrusted archives and refrain from opening generated reports in browsers until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WinrarApplication
Affected:= 7.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WinRAR version
    Open WinRAR, go to Help > About WinRAR, or right-click the winrar.exe file and view Properties > Details to confirm the exact version number
    Affected if Version is exactly 7.11
  2. Locate generated HTML reports
    Search for .html files in common report output directories: %USERPROFILE%\Documents\WinRAR Reports, %USERPROFILE%\Downloads, or custom paths configured in WinRAR settings
    Affected if HTML report files exist that were generated using WinRAR 7.11
  3. Inspect archived file names in reports
    Open any found HTML report files in a text editor and search for archived file name entries within the report data
    Affected if Report contains file names from archives that include unescaped HTML special characters like <, >, or script tags
  4. Check for suspicious archive file names
    Review recent archives opened in WinRAR 7.11 and examine their contained file names for patterns resembling HTML/script injection payloads
    Affected if Archives with file names containing <script>, javascript:, or similar HTML/JS patterns were processed and reports were generated

User is affected if WinRAR version is exactly 7.11 AND HTML reports have been generated from archives, particularly untrusted ones, since the vulnerability requires the report generation feature to be used with malicious file names.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Await vendor patch from Rarlab. Users should avoid generating reports from untrusted archives and refrain from opening generated reports in browsers until patched.

Recommended fix Moderate confidence

WinRAR 7.12 or later (check official rarlab.com/win-rar.com for latest available version)

  1. 1. Visit the official WinRAR website (www.win-rar.com) or Rarlab (www.rarlab.com) to check for the latest version.
  2. 2. Download the most recent WinRAR version available (version 7.12 or later).
  3. 3. Uninstall the current WinRAR 7.11 installation.
  4. 4. Install the newly downloaded version.
  5. 5. When using the 'Generate Report' feature, ensure you trust the source of archive files being processed, as the report is generated as an HTML file.
  6. 6. Exercise caution when opening generated HTML reports from untrusted sources.
Caveat Minor - typical version upgrade with potential minor UI changes; ensure any automation/scripts compatible with command-line parameters are tested

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Winrar Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52331 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data