LiveActive security incident?Get immediate response
CVE Record

CVE-2025-56219: Incorrect access control in SigningHub v8.6.8 allows attackers to arbitrarily add user accounts without any...

Incorrect access control in SigningHub v8.6.8 allows attackers to arbitrarily add user accounts without any rate limiting. This can lead to a resource exhaustion and a Denial of Service (DoS) when an excessively large number of user accounts are created.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-56219 affects SigningHub v8.6.8. A low-privileged attacker can add large numbers of user accounts because access control and rate limiting are insufficient. The main business risk is service disruption from resource exhaustion; integrity impact is limited to unauthorized account creation.

Executive priority

Treat this as high priority for exposed SigningHub environments because availability impact is high and exploitation requires only low privileges. Prioritize confirming affected deployments, reducing access, and obtaining vendor remediation guidance.

Technical view

The CVE describes CWE-284 incorrect access control in SigningHub v8.6.8. CVSS 3.1 is 7.1 high: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, low integrity impact, high availability impact.

Likely exposure

Exposure is most likely for internet-facing or broadly accessible SigningHub v8.6.8 deployments where low-privileged users can reach account creation or registration functionality. The bundle does not provide CPEs or a broader affected-version range.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. A public GitHub reference is listed, but the provided evidence only supports the described vulnerability and does not prove exploitation in the wild.

Researcher notes

Evidence is limited. The CVE names SigningHub v8.6.8, CWE-284, and DoS through unrestricted account creation, but affected vendor/product metadata is listed as n/a and no patch details are provided in the bundle.

Mitigation direction

  • Check SigningHub vendor guidance for fixed versions or supported mitigations.
  • Restrict access to user creation and registration workflows.
  • Apply rate limiting or abuse controls where administratively available.
  • Monitor for abnormal account creation volume and resource spikes.
  • Disable unused self-service account creation paths if business operations allow.

Validation and detection

  • Confirm whether any SigningHub instance is running v8.6.8.
  • Review who can create or trigger new user accounts.
  • Check logs for sudden account growth or repeated creation attempts.
  • Verify rate limiting or abuse controls around account creation.
  • Track vendor advisories because the bundle names no specific patch.
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-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-56219 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H2.84.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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

Source materials

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-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.