LiveActive security incident?Get immediate response
CVE Record

CVE-2025-56572: An issue in finance.js v.4.1.0 allows a remote attacker to cause a denial of service via the seekZero() par...

An issue in finance.js v.4.1.0 allows a remote attacker to cause a denial of service via the seekZero() parameter.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-56572 is a denial-of-service issue reported in finance.js v4.1.0. A remote, unauthenticated attacker may be able to trigger excessive resource use through the seekZero() parameter, affecting availability. The public record does not identify a vendor patch or confirmed exploitation.

Executive priority

Treat this as a high-priority availability risk if finance.js v4.1.0 is used in internet-facing workflows. If the library is not present or not exposed to remote input, urgency drops, but teams should still document the decision.

Technical view

The CVE describes CWE-400 resource consumption in finance.js v4.1.0, reachable over the network with low complexity and no privileges or user interaction. CVSS 3.1 is 7.5: availability impact is high, with no stated confidentiality or integrity impact. Affected CPE data is absent.

Likely exposure

Exposure is most likely in applications that depend on finance.js v4.1.0 and pass remote or user-controlled values into functionality involving seekZero(). The CVE record does not provide package ecosystem identifiers or complete affected-product metadata.

Exploitation context

CISA KEV status in the bundle is false, and no cited source confirms active exploitation. The vulnerability is still operationally relevant because the CVSS vector indicates network reachability, no authentication requirement, and high availability impact.

Researcher notes

Evidence is limited: the CVE names finance.js v4.1.0 and seekZero(), but affected vendor/product fields and CPEs are n/a. Do not assume broader version impact, exploit activity, or a fixed release without upstream confirmation.

Mitigation direction

  • Check the upstream finance.js repository and advisory sources for fixed versions or maintainer guidance.
  • Inventory applications using finance.js v4.1.0 or vendored copies of the referenced source file.
  • Restrict remote or user-controlled access to code paths invoking seekZero() where feasible.
  • Apply input bounds, execution limits, and availability monitoring around exposed financial-calculation services.
  • Prioritize replacement or upgrade if upstream provides a maintained fixed release.

Validation and detection

  • Search dependency manifests and lockfiles for finance.js v4.1.0.
  • Review application code for remote inputs flowing into seekZero()-related calculations.
  • Confirm whether affected services expose the vulnerable path to unauthenticated users.
  • Check service telemetry for resource exhaustion or availability spikes around calculation endpoints.
  • Track the CVE record and upstream repository for patch or scope updates.
Prepared
Confidence
medium
Sources
5

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 · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2025-56572 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:N/I:N/A:H

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
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
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-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.