dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-54122

CRITICAL · 10.0 CVSS v3.1 Published 2025-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Manager-io/Manager is accounting software. A critical unauthenticated full read Server-Side Request Forgery (SSRF) vulnerability has been identified in the proxy handler component of both manager Desktop and Server edition versions up to and including 25.7.18.2519. This vulnerability allows an unauthenticated attacker to bypass network isolation and access restrictions, potentially enabling access to internal services, cloud metadata endpoints, and exfiltration of sensitive data from isolated network segments. This vulnerability is fixed in version 25.7.21.2525.

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

An unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the proxy handler component of Manager io/Manager allows attackers to make arbitrary HTTP requests from the server without authentication. This enables bypass of network isolation to access internal services, cloud metadata endpoints (such as AWS IMDS), and exfiltration of sensitive data from isolated network segments.

MitigationUpgrade to version 25.7.21.2525 or later immediately. In the interim, restrict network access to the Manager server and disable or firewall the proxy handler component if possible.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Check Manager io/Manager version
    Locate the installed Manager application and retrieve its version number (typically found in About, Help, or the application itself). Compare it against the affected range: versions prior to 25.7.21.2525 are vulnerable.
    Affected if Installed version is before 25.7.21.2525
  2. Identify proxy handler component exposure
    Examine the Manager application configuration or web interface for proxy-related settings or endpoints. Look for any proxy handler, URL fetcher, or similar functionality that processes external requests.
    Affected if Proxy handler component is enabled or accessible without authentication
  3. Verify network accessibility
    Determine if the Manager service is exposed to untrusted networks or the internet. Check firewall rules, network ACLs, and service binding addresses.
    Affected if Manager service is reachable from untrusted networks without network segmentation
  4. Inspect proxy configuration logs
    Review application logs for any suspicious outbound HTTP requests, particularly to internal IPs (127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unusual internal destinations.
    Affected if Logs show requests to internal services or metadata endpoints that were not initiated by legitimate users

You are affected if running any version of Manager io/Manager before 25.7.21.2525 with the proxy handler component enabled and accessible on a network where attackers can reach the service.

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

Upgrade to version 25.7.21.2525 or later immediately. In the interim, restrict network access to the Manager server and disable or firewall the proxy handler component if possible.

Recommended fix High confidence

25.7.21.2525

  1. Upgrade Manager-io/Manager to version 25.7.21.2525 or later for both Desktop and Server editions
  2. After upgrading, verify the proxy handler component no longer accepts unauthenticated external requests

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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