LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36723: Emuse - eServices / eNvoice Exposure Of Private Personal Information

Emuse - eServices / eNvoice Exposure Of Private Personal Information due to lack of identification mechanisms and predictable IDs an attacker can scrape all the files on the service.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-36723 describes a privacy exposure in Emuse eServices/eNvoice where weak identification controls and predictable IDs could let an attacker scrape personal files from the service. The business concern is unauthorized disclosure of private personal information, not system takeover.

Executive priority

Prioritize confirmation if the organization uses Emuse eServices/eNvoice for personal files. The severity is medium, but the data impact can be significant because the described weakness involves potential exposure of private personal information.

Technical view

The record maps to CWE-359 and carries CVSS 3.1 score 6.1, medium severity. Sources describe missing identification mechanisms and predictable identifiers enabling file scraping. The affected entry only names Emuse eServices/eNvoice in Production, with no CPEs or detailed fixed versions.

Likely exposure

Organizations using Emuse eServices/eNvoice production instances, especially where personal files are stored behind predictable identifiers. The sources do not provide product build numbers, CPEs, or deployment prerequisites, so asset owners must confirm exposure with vendor or deployment records.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. The described issue is plausible for unauthorized data collection if an exposed deployment allows access to personal files without strong identity or authorization checks.

Researcher notes

Evidence is limited. The description cites predictable IDs and absent identification mechanisms, while the CVSS vector lists local attack vector and user interaction. Treat affected scope and remediation status as unresolved unless confirmed by the vendor advisory.

Mitigation direction

  • Check Emuse or gov.il advisory channels for official remediation guidance.
  • Identify any production use of Emuse eServices/eNvoice in your environment.
  • Restrict access to sensitive file endpoints while vendor guidance is confirmed.
  • Review document access controls for authentication and authorization enforcement.
  • Assess privacy incident response needs if exposure is confirmed.

Validation and detection

  • Inventory deployments matching Emuse eServices/eNvoice Production.
  • Review access logs for abnormal sequential or high-volume file requests.
  • Confirm personal files are not reachable by predictable identifiers alone.
  • Verify access requires authenticated, authorized user context.
  • Document uncertainty where vendor version or patch data is unavailable.
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 · low confidence lookup

CWE-359: 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-2021-36723 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
6.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/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
0Timeline events
0ADP providers
2Source links

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
6.1CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N1.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-36723Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EmuseeServices / eNvoiceProductionListed
Weakness

CWE details

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

CWE-359 · source CWE mapping

Exposure of Private Personal Information to an Unauthorized Actor

Exposure of Private Personal Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.