Analyst readout for executives and security teams
Plain-English summary
CVE-2026-12213 is an improper authorization issue in Huly Platform through 0.7.0. A logged-in remote user may access limited user information they should not be allowed to see. Public exploit information exists, but the provided sources do not show active exploitation or a vendor fix.
Executive priority
Treat as a near-term security hygiene item, not an emergency based on current evidence. Prioritize if Huly is internet-facing, widely used internally, or contains sensitive user profile data.
Technical view
The issue affects getAccountInfo in server/account/src/operations.ts, part of the User Information Handler. VulDB describes authorization bypass involving user-controlled SQL primary key handling. CVSS v4.0 is 5.3, with network access, low complexity, low privileges required, no user interaction, and low confidentiality impact.
Likely exposure
Organizations running hcengineering Huly Platform versions 0.1 through 0.7.0 are potentially exposed, especially internet-accessible or broadly accessible instances with many authenticated users.
Exploitation context
The vulnerability is remotely reachable and requires low privileges. VulDB states the exploit has been made public. The provided data does not indicate CISA KEV listing or confirmed active exploitation.
Researcher notes
Sources attribute the flaw to improper authorization in getAccountInfo. The submission references authorization bypass via user-controlled SQL primary key. Vendor response and patch status are not available in the provided sources, so remediation specifics remain uncertain.
Mitigation direction
- Identify all Huly Platform deployments and versions.
- If running 0.7.0 or earlier, check hcengineering guidance for fixes or workarounds.
- Limit Huly access to trusted authenticated users where practical.
- Monitor vendor and CVE sources for a fixed release or advisory.
Validation and detection
- Confirm whether deployed Huly Platform versions are 0.7.0 or earlier.
- Review access controls around user information functions.
- Check application logs for unusual account information access patterns.
- Track whether the vendor publishes remediation guidance.
Public sources used
Based on public source material and reviewed before publication.
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-266: 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 lookupCWE-285: 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 lookupCVE-2026-12213 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
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.
CVSS vector scores
4 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P — — VulDB CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R 2.8 1.4 VulDB CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R 2.8 1.4 VulDB AV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:ND/RC:UR 8 2.9 VulDB Vulnerability scoring details
Base CVSS 4.0 score
5.3 MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
4.3 MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
Base CVSS 3.0 score
4.3 MediumVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
Base CVSS 2.0 score
4 MediumVector: AV:N/AC:L/Au:S/C:P/I:N/A:N/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 source CVE List V5
- VDB-370855 | hcengineering Huly Platform User Information operations.ts getAccountInfo improper authorization CVE reference, VulDB · vdb-entry, technical-description
- VDB-370855 | CTI Indicators (IOB, IOC, TTP, IOA) CVE reference, VulDB · signature, permissions-required
- CVE-2026-12213 | CVE Analysis and Report CVE reference, VulDB · third-party-advisory
- Submit #832974 | Huly hcengineering/platform <= 0.7.0 (confirmed on commit 18ef71b) Authorization Bypass Through User-Controlled SQL Primary Key CVE reference, VulDB · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.