Songloft 2.9.0 before 2.13.6 Hardcoded Admin Credentials in Embedded Backend
Songloft 2.9.0 through 2.13.5 is affected when the server starts without admin credentials set via flags or environment variables, so built-in defaults apply. Fixed in 2.13.6.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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? →
- Unclear
- Fix
- Fixed in 2.13.6
- 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: poc
- Automatable: no
- Technical impact: total
Summary
Songloft 2.9.0 before 2.13.6 contains a hardcoded credentials vulnerability that allows adjacent network attackers to authenticate as administrator using the fixed admin/admin pair. Attackers on the same network can log in via the /api/v1/auth/login endpoint to modify library and configuration settings and install JavaScript plugins running in QuickJS.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- songloft-org songloft
From 2.9.0 · fixed in 2.13.6
References 7
GitHub · songloft-org/songloft
Questions about CVE-2026-119662
What does this mean?
When the server starts without an admin username and password set via flags or environment variables, it assigns literal built-in default credentials. Logging in with those defaults gives full administrator access, including the admin API, library and config changes, log export, and installation of JavaScript plugins that run with file-system and network access.Source: github.com
Am I affected, and how do I check?
The vendor states that v2.13.5 and earlier are affected, starting from 2.9.0. To check a setup, confirm whether the admin username and password are set via flags or environment variables; if neither is set, the built-in defaults apply.Source: github.com
What should I do about it?
Upgrade Songloft to 2.13.6 or later, which is the fixed version listed for this range.Source: github.com
Is it 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data