CVE
STEL Order unauthorized employee data access in Tempo module
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The STEL Order Tempo module is affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
STEL Order's Tempo module has an insecure direct object reference flaw: the server returns employee data based on an `empleadoId` parameter without checking whether the user is allowed to see it. A remote attacker with a low-privilege authenticated account can change that parameter to view other employees' first and last names, roles, job titles, and vacation days.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Insecure direct object reference (IDOR) in the STEL Order Tempo module. The server retrieves data based on the empleadoId parameter without checking the user's permissions. By modifying this parameter, an authenticated user can view the first name, last name, role, job title, and vacation days of other employees.
Who should check
Teams running the STEL Order Tempo module, a business management web application; no vendor fix has been reported yet.
“Insecure direct object reference (IDOR) in the STEL Order Tempo module.”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The STEL Order Tempo module is affected.Workaround: The checked facts give no workaround. Limiting which users can reach the Tempo module would narrow exposure, since the issue requires an authenticated user.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127044 (Insecure direct object references in STEL Order), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127044 (entry last updated 2026-11-16):
Affected:
- STEL Order STEL Order: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The STEL Order Tempo module is affected. (source: https://www.incibe.es/en/incibe-cert/notices/aviso/insecure-direct-object-references-mygestion-and-stel-order)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-127044 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127044 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.incibe.es/en/incibe-cert/notices/aviso/insecure-direct-object-references-mygestion-and-stel-order
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127044
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127044"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- STEL Order STEL Order
Version range not reported
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127044
Is CVE-2026-127044 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An insecure direct object reference in the STEL Order Tempo module lets an authenticated user view the first name, last name, role, job title, and vacation days of other employees.Source: incibe.es
Am I affected, and how do I check?
The checked facts name the STEL Order Tempo module but list no affected versions. A reader can check whether the Tempo module is installed in their STEL Order setup.Source: incibe.es
How do I fix CVE-2026-127044?
The checked facts name no fixed version and no vendor patch, so no upgrade target is available from these facts.Source: incibe.es
What if there's no patch?
The checked facts give no workaround. Limiting which users can reach the Tempo module would narrow exposure, since the issue requires an authenticated user.Source: incibe.es