CVE-2025-56223: A lack of rate limiting in the component /Home/UploadStreamDocument of SigningHub v8.6.8 allows attackers t...
A lack of rate limiting in the component /Home/UploadStreamDocument of SigningHub v8.6.8 allows attackers to cause a Denial of Service (DoS) via uploading an excessive number of files.
Security readout for executives and security teams
Plain-English summary
CVE-2025-56223 is a high-severity denial-of-service issue reported in SigningHub v8.6.8. The upload stream document endpoint lacks rate limiting, allowing unauthenticated network attackers to overload availability by submitting excessive file uploads. Sources do not identify a vendor patch or confirmed exploitation.
Executive priority
Treat this as a near-term availability risk for exposed SigningHub deployments. Prioritize asset confirmation, exposure reduction, and vendor remediation tracking before broader emergency response unless local abuse is observed.
Technical view
The issue is mapped to CWE-770 and affects /Home/UploadStreamDocument in SigningHub v8.6.8. CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating remote, low-complexity availability impact without authentication or user interaction.
Likely exposure
Exposure is likely limited to organizations running SigningHub v8.6.8 with the upload endpoint reachable from the internet or untrusted networks. The provided CVE affected-product metadata is incomplete, so validate installed product and version locally.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The sources support a denial-of-service risk through excessive uploads, but they do not establish active exploitation in the wild or provide confirmed attacker activity.
Researcher notes
Evidence is thin: the CVE description, CVSS vector, CWE mapping, and one GitHub reference define the issue. The bundle’s affected-product fields are n/a despite the description naming SigningHub v8.6.8, so avoid overgeneralizing affected versions.
Mitigation direction
Check SigningHub vendor guidance for patched versions or configuration mitigations.
Prioritize upgrading or applying vendor-provided fixes when available.
Add upstream rate limiting and request body controls for upload routes where supported.
Restrict upload endpoint access to trusted networks where business workflows allow.
Monitor upload volume, storage growth, and availability metrics for abuse indicators.
Validation and detection
Confirm whether any SigningHub v8.6.8 instances are deployed.
Determine whether /Home/UploadStreamDocument is reachable from untrusted networks.
Review WAF, proxy, and application logs for abnormal upload bursts.
Check current rate limits, body-size limits, and storage quotas around uploads.
Track vendor advisories because the provided sources do not name a patch.
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-770: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.