LiveActive security incident?Get immediate response
CVE Record

CVE-2026-84148: Insecure Direct Object Reference Vulnerability in Manacle Technologies ERP System

This vulnerability exists in the ERP system due to improper authentication and authorization controls in the API endpoint. An unauthenticated remote attacker could exploit this vulnerability by manipulating parameter which could lead to exposure of sensitive information belonging to other users on the targeted system.

CriticalCVSS 9.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A critical access-control flaw in Manacle Technologies’ multi-tenant ERP API may let an unauthenticated internet attacker alter an object identifier and view sensitive information belonging to other users. The supplied record reports confidentiality exposure across both the vulnerable system and connected systems, but no data modification or service disruption.

Executive priority

Treat as an urgent confidentiality risk. Immediately identify exposed Manacle ERP systems, contact the vendor for authoritative applicability and remediation, and restrict API exposure meanwhile. Prioritize investigation where the platform stores customer, employee, financial, or regulated information. The critical score warrants rapid action, although active exploitation is not established by the supplied evidence.

Technical view

CVE-2026-84148 is classified as CWE-639, an authorization bypass through a user-controlled key. The API reportedly fails to authenticate and authorize object access correctly. Its CVSS 4.0 score is 9.2: network-accessible, low complexity, no privileges, no user interaction, and high confidentiality impact. The source bundle does not identify the endpoint or usable affected-version range.

Likely exposure

Potentially exposed organizations are those operating an affected Manacle Technologies multi-tenant ERP deployment, particularly where its API is internet-accessible. The supplied version value is incomplete, no CPE is provided, and the default status is listed as unaffected; therefore, inventory matching cannot be performed reliably from this bundle alone.

Exploitation context

The weakness is described as remotely exploitable without authentication or user interaction by manipulating a parameter. However, the bundle marks the CVE as absent from KEV and supplies no evidence of exploitation in the wild, public proof-of-concept availability, or confirmed victim activity.

Researcher notes

The record supports an IDOR-style authorization failure but omits the endpoint, parameter, deployment model, precise versions, discovery details, patch information, and exploitation evidence. The placeholder-like version value and unaffected default status materially limit exposure assessment. Testing should remain authorized and focus on authentication, object-level authorization, and tenant-boundary enforcement without accessing real user data.

Mitigation direction

  • Check Manacle Technologies and CERT-In guidance for confirmed affected versions and an official remediation.
  • Apply the vendor-provided update or mitigation when identified.
  • Temporarily restrict ERP API access to trusted networks or authenticated gateways where operationally feasible.
  • Monitor ERP API requests and sensitive-record access for unexpected identifiers or cross-tenant activity.
  • Review potentially exposed data and activate incident-response procedures if unauthorized access is suspected.

Validation and detection

  • Inventory Manacle Technologies ERP deployments, versions, hosting locations, and exposed API interfaces.
  • Confirm affected status directly with the vendor because the supplied version data is incomplete.
  • Verify every API object request enforces authentication, tenant isolation, and record-level authorization.
  • Review logs for unauthenticated requests and accounts accessing records outside their assigned tenant.
  • After remediation, perform authorized negative tests confirming cross-user and cross-tenant records remain inaccessible.
Prepared
Confidence
medium
Sources
3

Public sources used

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

CVE-2026-84148 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
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA: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
2Source 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
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——CERT-In

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-84148Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
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
Manacle TechnologiesMulti-tenant ERP Systemversionunaffected
Weakness

CWE details

CWE-639

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

CWE-639 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.

Open CWE intelligenceSame-CWE CVEs