LiveActive security incident?Get immediate response
CVE Record

CVE-2025-10912: IDOR in saastech.io's TemizlikYolda

Authorization Bypass Through User-Controlled Key vulnerability in Saastech Cleaning and Internet Services Inc. TemizlikYolda allows Manipulating User-Controlled Variables. This issue affects TemizlikYolda: through 11022026. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-10912 is an authorization bypass issue in Saastech TemizlikYolda. A logged-in user may be able to manipulate user-controlled identifiers to affect data or functions they should not control. The public record rates it medium severity. No source provided confirms active exploitation or a vendor fix.

Executive priority

Treat this as a moderate-priority application security issue. It is not currently supported by public evidence of active exploitation, but it may allow authorized users to bypass intended limits. Prioritize inventory, vendor clarification, and compensating controls if the product handles business-critical workflows.

Technical view

The issue is classified as CWE-639, Authorization Bypass Through User-Controlled Key, commonly called IDOR. The CVSS v3.1 score is 5.4 with network access, low complexity, low privileges, and no user interaction. Impact is listed as low integrity and low availability, with no confidentiality impact in the CVSS vector.

Likely exposure

Exposure appears limited to organizations using Saastech Cleaning and Internet Services Inc. TemizlikYolda versions through 11022026. Public data does not clarify deployment models, affected components, or whether cloud-hosted instances are automatically updated.

Exploitation context

The CVE record says exploitation requires low privileges but no user interaction and is network-accessible. The provided sources do not state that exploitation is occurring in the wild, and the CVE is not marked as CISA KEV.

Researcher notes

The public record is sparse. It names the weakness class, product, vendor, affected range, CVSS vector, and notes that the vendor did not respond. It does not provide technical detail, proof of exploitation, patch information, or clear product version semantics beyond “through 11022026.”

Mitigation direction

  • Identify whether TemizlikYolda is used in your environment.
  • Check vendor or government advisories for updated remediation guidance.
  • Limit application access to trusted users where operationally possible.
  • Review role and tenant authorization controls for sensitive workflows.
  • Monitor application logs for unusual cross-account or cross-record activity.

Validation and detection

  • Confirm deployed TemizlikYolda version and hosting model.
  • Check whether the instance falls within versions through 11022026.
  • Review access-control test coverage for user-controlled object identifiers.
  • Assess logs for unauthorized changes or unexpected record access patterns.
  • Document any compensating controls if no vendor fix is available.
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-10912 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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
Saastech Cleaning and Internet Services Inc.TemizlikYolda0unknown
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.