dbcve.org
Sage Frp 1000Application · Sage

CVE-2019-25053

HIGH · 7.5 CVSS v3.1 Published 2023-01-27
Fix available
A fix is available. Upgrade to 2019-11 or later.
See remediation →
84/100
Remediation priority · High
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
A path traversal vulnerability exists in Sage FRP 1000 before November 2019. This allows remote unauthenticated attackers to access files outside of the web tree via a crafted URL.

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

A path traversal vulnerability in Sage FRP 1000 allows remote unauthenticated attackers to access files outside the web document root by using directory traversal sequences in crafted URLs.

MitigationUpdate Sage FRP 1000 to the November 2019 or later release; if patching is not feasible, implement network segmentation and restrict web server access to prevent unauthorized filesystem traversal.

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
Sage Frp 1000Application
Affected:< 2019-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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm Sage FRP 1000 installation
    Identify whether Sage FRP 1000 is installed on the system by checking installed software, application directories, or running processes related to the Sage FRP product.
    Affected if Sage FRP 1000 is present on the system
  2. Determine installed version
    Locate the version information for Sage FRP 1000 through the application itself (typically accessible via the admin interface, about page, or in installation/log files), then compare it to the affected range of versions before November 2019.
    Affected if The installed version is earlier than the November 2019 release (version < 2019-11)
  3. Verify web server component is active
    Check if the web server component of Sage FRP 1000 is running and accessible. This may involve checking if the HTTP/HTTPS service is listening on expected ports (commonly port 80/443 or custom web ports).
    Affected if The web interface is exposed and reachable
  4. Check network exposure
    Determine whether the web server is accessible from network segments outside the trusted internal network, such as from the public internet or untrusted VLANs.
    Affected if The web interface is accessible from untrusted network locations
  5. Test for directory traversal vulnerability
    Send a crafted HTTP request containing directory traversal sequences (such as ../../) to the web server endpoint to verify if arbitrary filesystem access is possible outside the document root.
    Affected if The server responds with content from paths outside the web document root

The environment is affected if Sage FRP 1000 version earlier than November 2019 is installed and the web interface is accessible, as this combination allows remote unauthenticated path traversal attacks.

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
Upgrade available Upgrade to 2019-11 or later
Fixed in 2019-11
Interim mitigation

Update Sage FRP 1000 to the November 2019 or later release; if patching is not feasible, implement network segmentation and restrict web server access to prevent unauthorized filesystem traversal.

Recommended fix Moderate confidence

Sage FRP 1000 November 2019 release or later

  1. 1. Identify the current version of Sage FRP 1000 installed
  2. 2. Verify the installed version is before November 2019 (vulnerable)
  3. 3. Backup all current configurations and data
  4. 4. Obtain the November 2019 or later release of Sage FRP 1000 from the vendor
  5. 5. Perform the upgrade following Sage installation documentation
  6. 6. Verify the upgrade was successful and the version is November 2019 or later
  7. 7. Test that the path traversal vulnerability is no longer exploitable

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

Fix this in Sage Frp 1000 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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