CVE-2026-129469

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-11-15. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-126019 (ENISA EUVD) · GHSA-8pjf-7rrv-hw3r (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Course-tencent-cloud before 2.0.2 contains an insecure direct object reference vulnerability that allows unauthenticated attackers to view other users' refund previews by supplying an order sn to /api/refund/confirm. Attackers can compute valid sn values from Sqids-encoded sequential order ids using the default key to disclose ordered items, prices, refund amounts, fees and deadlines.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 15, 2026

Last Modified

November 16, 2026

Advisory Details (6)

Auto-updated Nov 15, 2026
Patch available. Sources: github_commit.
Web page

Course-tencent-cloud before 2.0.2 IDOR via /api/refund/confirm | Advisories | VulnCheck

https://www.vulncheck.com/advisories/course-tencent-cloud-before-2.0.2-idor-via-api-refund-confirm
Web page

course-tencent-cloud/app/Http/Home/Controllers/RefundController.php at v2.0.1 · xiaochong0302/course-tencent-cloud · GitHub

https://github.com/xiaochong0302/course-tencent-cloud/blob/v2.0.1/app/Http/Home/Controllers/RefundController.php#L49-L64
Web page

course-tencent-cloud/app/Http/Api/Controllers/RefundController.php at v2.0.1 · xiaochong0302/course-tencent-cloud · GitHub

https://github.com/xiaochong0302/course-tencent-cloud/blob/v2.0.1/app/Http/Api/Controllers/RefundController.php#L24-L33
GitHub commit Patch Available

commit 8e8bcb4e1379 (xiaochong0302/course-tencent-cloud)

Patch available: xiaochong0302/course-tencent-cloud v2.0.2 (contains commit 8e8bcb4e1379)

https://github.com/xiaochong0302/course-tencent-cloud/commit/8e8bcb4e13795006e16d51158790ce3120c8164a
Web page

Security: Course-Tencent-Cloud (koogua online school) refund confirm endpoints disclose another user's order and refund data (missing owner check) · Issue #38 · xiaochong0302/course-tencent-cloud · GitHub

https://github.com/xiaochong0302/course-tencent-cloud/issues/38
Web page

Course-Tencent-Cloud (koogua online school) refund confirm endpoints disclose another user's order and refund data (missing owner check) - HackMD

https://hackmd.io/@hieund/course-tencent-cloud-refund-confirm-missing-owner-check-idor

Vendor Advisories for CVE-2026-129469(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-19 22:58 UTCEchelonGraph re-scored
  4. 2026-11-19 22:58 UTCGHSA enrichmentGHSA-8pjf-7rrv-hw3r · GitHub severity MODERATE · GitHub CVSS 5.3
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-11-16 19:38 UTCEchelonGraph re-scored
  9. 2026-11-16 19:38 UTCGHSA enrichmentGHSA-8pjf-7rrv-hw3r · GitHub severity MODERATE · GitHub CVSS 5.3
  10. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-11-15 15:47 UTCEchelonGraph re-scored
  12. 2026-11-15 15:47 UTCGHSA enrichmentGHSA-8pjf-7rrv-hw3r · GitHub severity MODERATE · GitHub CVSS 5.3
  13. 2026-11-15 13:29 UTCEchelonGraph re-scored
  14. 2026-11-15 13:02 UTCENISA EUVD ID recordedEUVD-2026-126019 · Source: ENISA EUVD
  15. 2026-11-15 12:49 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
  16. 2026-11-15 12:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129469?
CVE-2026-129469 is a medium-severity vulnerability; its CVE record was published on November 15, 2026. Course-tencent-cloud before 2.0.2 contains an insecure direct object reference vulnerability that allows unauthenticated attackers to view other users' refund previews by supplying an order sn to /api/refund/confirm. Attackers can compute valid sn values from Sqids-encoded sequential order ids…
When was CVE-2026-129469 made public?
CVE-2026-129469 was made public on November 14, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 15, 2026. EchelonGraph's copy of the record carries a last-modified date of November 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129469 actively exploited?
CVE-2026-129469 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129469?
CVE-2026-129469 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129469?
A fix for CVE-2026-129469 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129469 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-129469

Explore →

Is Your Infrastructure Affected by CVE-2026-129469?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.