dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-4477

HIGH · 7.2 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
The ThreatSonar Anti-Ransomware from TeamT5 has a Privilege Escalation vulnerability, allowing remote attackers with intermediate privileges to escalate their privileges to highest administrator level through a specific API.

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 · moderate confidence

ThreatSonar Anti-Ransomware from TeamT5 contains a privilege escalation vulnerability allowing remote attackers with intermediate privileges to elevate to highest administrator privileges through a specific API endpoint. The vulnerability stems from insufficient authorization validation on the targeted API, enabling privilege boundary bypass.

MitigationImplement proper authorization checks on the affected API endpoint to verify the requester's privilege level matches the requested operation. Apply principle of least privilege to API access controls and validate all permission requests server-side.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm ThreatSonar Anti-Ransomware is installed
    Check for ThreatSonar Anti-Ransomware installation by reviewing installed programs on the system, or locate the installation directory (typically under C:\Program Files\TeamT5\ThreatSonar or similar paths on Windows). Use commands like 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*ThreatSonar*"}' on Windows or check package managers on Linux systems.
    Affected if ThreatSonar Anti-Ransomware is present on the system
  2. Identify the installed version
    Locate the version information in the product's installation directory, configuration files, or by querying the service/daemon. Common locations include a 'version.txt' file, 'about' dialog in the GUI, or metadata in the service executable. Compare the installed version against any publicly available version information for ThreatSonar.
    Affected if The installed version cannot be confirmed as patched or is earlier than the fixed version released after CVE-2025-4477
  3. Verify API endpoint accessibility
    Identify if the API endpoint involved in the privilege escalation is exposed and accessible. Review web server configuration files, reverse proxy settings, or API gateway configurations that may expose ThreatSonar's administrative interfaces. Check network exposure of the management console ports.
    Affected if The administrative API endpoint is accessible from network segments accessible to intermediate-privilege users or untrusted networks
  4. Review API authorization configuration
    Inspect the authorization configuration files for the ThreatSonar API service. Look for role-based access control (RBAC) settings, API permission mappings, and endpoint-level authorization rules in configuration files (typically XML, JSON, or YAML formats within the installation directory or config folders).
    Affected if Authorization rules allow intermediate-privilege users to access administrative API functions or lack explicit privilege level validation on sensitive endpoints
  5. Audit user roles and privileges
    Review the assigned roles and privilege levels of users configured in ThreatSonar. Check if any user accounts are assigned intermediate-level privileges that should not have access to administrative functions. Examine group memberships and permission assignments in the product's user management interface or configuration.
    Affected if Users with intermediate privileges can successfully invoke API calls that should require administrator-level authorization

A defender is affected if ThreatSonar Anti-Ransomware is installed, the API endpoint is accessible, and the authorization controls permit intermediate-privilege users to perform administrative operations through the vulnerable API path.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on the affected API endpoint to verify the requester's privilege level matches the requested operation. Apply principle of least privilege to API access controls and validate all permission requests server-side.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4477 — 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-4477 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