LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25053: A path traversal vulnerability exists in Sage FRP 1000 before November 2019.

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Sage FRP 1000 systems from before November 2019 may let an unauthenticated remote attacker read files outside the intended website area. The business risk is exposure of sensitive local files through the web interface, not confirmed system takeover.

Executive priority

Treat this as high priority for any exposed legacy Sage FRP 1000 system because it can disclose sensitive files without credentials. Urgency is lower if the product is absent, internal-only, or confirmed updated beyond the affected window.

Technical view

CVE-2019-25053 is a CWE-22 path traversal issue in Sage FRP 1000 before November 2019. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, indicating remote unauthenticated file-read risk with high confidentiality impact.

Likely exposure

Exposure is most likely where Sage FRP 1000 is reachable over a network, especially internet-facing or partner-facing deployments running builds before November 2019. The source bundle lacks CPEs and precise version ranges, so inventory confirmation is required.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. Public details state remote unauthenticated attackers can access files outside the web tree using a crafted URL, but no exploit prevalence is provided.

Researcher notes

The affected metadata in the bundle is sparse despite the title naming Sage FRP 1000. Avoid broad product assumptions. Focus validation on confirmed deployments, version dating, network reachability, and confidentiality impact.

Mitigation direction

  • Identify any Sage FRP 1000 deployments and their build dates.
  • Prioritize removal or isolation of internet-facing pre-November 2019 instances.
  • Check Sage or maintainer guidance for supported fixed versions or compensating controls.
  • Restrict web access to trusted networks where immediate upgrade is not possible.
  • Review logs for unusual file access patterns around the web interface.

Validation and detection

  • Confirm whether Sage FRP 1000 exists in asset inventory.
  • Verify deployed version or build date against the pre-November 2019 affected statement.
  • Check external exposure through approved asset management or perimeter scanning data.
  • Review web server logs for traversal-like requests without replaying exploit patterns.
  • Confirm remediation by documenting vendor guidance, upgrade status, or isolation controls.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25053 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2019-25053Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.