LiveActive security incident?Get immediate response
CVE Record

CVE-2025-8463: IDOR in SecHard Information Technologies' SecHard

Authorization Bypass Through User-Controlled Key vulnerability in SecHard Information Technologies SecHard allows Forceful Browsing. This issue affects SecHard: before 3.6.2-20250805.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-8463 is an authorization bypass in SecHard. A logged-in attacker may access information they should not be able to view by forcing access to controlled identifiers. The listed impact is confidentiality only. Systems running SecHard before 3.6.2-20250805 should be reviewed and prioritized for upgrade or vendor-directed remediation.

Executive priority

Address in the normal vulnerability management cycle, with higher priority where SecHard handles sensitive information or has many low-privileged users. The main business concern is unauthorized data access, not system takeover or outage, based on current public information.

Technical view

The CVE describes CWE-639, Authorization Bypass Through User-Controlled Key, enabling forceful browsing in SecHard Information Technologies SecHard before 3.6.2-20250805. CVSS 3.1 is 5.3: network exploitable, high complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is limited to organizations using SecHard versions before 3.6.2-20250805. The attacker must already have low-privileged access. Public sources do not identify specific modules, endpoints, deployments, or data types affected.

Exploitation context

No CISA KEV listing or cited source indicates active exploitation. The CVSS vector suggests remote exploitation is possible after authentication, but with high attack complexity. Treat this as a data exposure risk rather than a service disruption risk.

Researcher notes

Public details are sparse. The record names IDOR/forceful browsing but does not identify affected endpoints, parameters, or data objects. Avoid assuming exploitability beyond the CVSS and description. One referenced government URL is marked broken in the source bundle; corroborate with available vendor or government advisories.

Mitigation direction

  • Identify all SecHard deployments and their versions.
  • Upgrade SecHard to 3.6.2-20250805 or later where applicable.
  • Review vendor and government advisories for product-specific remediation guidance.
  • Restrict access to SecHard to trusted users and networks where possible.
  • Monitor for unusual access patterns by low-privileged accounts.

Validation and detection

  • Confirm whether any SecHard instance is older than 3.6.2-20250805.
  • Review role and object-access controls for sensitive records.
  • Check logs for unexpected access by authenticated low-privileged users.
  • Verify remediation against vendor guidance after upgrading.
  • Document any internet-exposed or broadly accessible SecHard interfaces.
Prepared
Confidence
medium
Sources
4

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

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-2025-8463 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/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
3Timeline events
1ADP providers
3Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N1.63.6TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2025-8463Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/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

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
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SecHard Information TechnologiesSecHard0unaffected
Weakness

CWE details

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.