Firekylin through 2.18.1 Improper Authorization via Admin REST API GET Actions
Only Firekylin 2.18.1 and earlier is in range, and exposure requires an editor-role account. CVSS scores it 7.1 (high). The vendor rating and a fixed version are not in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Firekylin version 2.18.1 or earlier Attacker holds a valid editor-role account
- 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? →
- 15/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
Summary
Firekylin, a Node.js blogging and content system, through version 2.18.1 has an improper authorization flaw that lets a logged-in editor-role user read administrator-only secrets over the network. An attacker can obtain TOTP secrets, push credentials, and cloud storage keys, or other users' app keys and secrets, which can then be used to publish posts as an administrator.
Read the original description
Firekylin through 2.18.1 contains an improper authorization vulnerability that allows editor-role users to read administrator-only secrets because the admin API base guard permits all GET actions. Editors can query options.js for TOTP secrets, push credentials, and cloud storage keys, or user.js for other users' app_key/app_secret to publish posts as administrators via admin/post_push.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Firekylin version 2.18.1 or earlier Attacker holds a valid editor-role accountApply the patch listed under Evidence.
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-125750 (Firekylin through 2.18.1 Improper Authorization via Admin REST API GET Actions), 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-125750 (entry last updated 2026-11-10): Affected: - firekylin Firekylin: through 2.18.1 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Firekylin version 2.18.1 or earlier (source: https://www.vulncheck.com/advisories/firekylin-through-2.18.1-improper-authorization-via-admin-rest-api-get-actions) - Attacker holds a valid editor-role account (source: https://hackmd.io/@hieund/cve-2026-125750-firekylin-admin-api-editor-missing-authz-secret-disclosure) Setup: the bug is reachable in a default setup; no special feature or setting is needed. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-125750 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125750 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://github.com/firekylin/firekylin/pull/976 - https://github.com/firekylin/firekylin/issues/975 - https://github.com/firekylin/firekylin/blob/2.18.1/src/controller/admin/api/base.js#L69-L77 - https://github.com/firekylin/firekylin/blob/2.18.1/src/controller/admin/api/options.js#L12-L41 - https://hackmd.io/@hieund/firekylin-admin-api-editor-missing-authz-secret-disclosure - https://www.vulncheck.com/advisories/firekylin-through-2.18.1-improper-authorization-via-admin-rest-api-get-actions - https://hackmd.io/@hieund/cve-2026-125750-firekylin-admin-api-editor-missing-authz-secret-disclosure 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-125750 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125750.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- firekylin Firekylin
through 2.18.1
Evidence 8
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 6
- Patch
- Report
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125750
Is CVE-2026-125750 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?
The admin REST API base guard permits all GET actions, so editor-role users can read admin-only secrets. These include TOTP seeds, push credentials, cloud storage keys, and other users' app_key and app_secret values. The advisory says those values can be used to publish posts as administrators or other authors.Source: vulncheck.com, hackmd.io
Which versions are affected by CVE-2026-125750?
Firekylin: through 2.18.1.Source: cve.now feed data
Am I affected, and how do I check?
Firekylin versions 2.18.1 and earlier are in range, with the introduced version listed as 0. The reported condition also requires a valid editor-role account. Compare the installed Firekylin version against 2.18.1 to see whether a given install falls in the stated range.Source: vulncheck.com, hackmd.io
How do I fix CVE-2026-125750?
The checked facts do not name a fixed version or a vendor patch, so no upgrade target can be stated from them. Check the Firekylin project or vendor for a release that goes past 2.18.1 before relying on any update.Source: vulncheck.com, hackmd.io