Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112296 Overview
CVE-2026-112296 is a default credentials vulnerability in FlyCms through commit edfdf724. The flaw ships a hardcoded super administrator account named flycms with the password admin123. Unauthenticated remote attackers can authenticate through the POST /api/auth/login endpoint by solving only the image captcha. Successful login grants full super administrator access, enabling complete control of site content, user accounts, and system configuration. The vulnerability is tracked under CWE-1392: Use of Default Credentials.
Critical Impact
Remote attackers can take over any default FlyCms deployment without exploiting a software bug, gaining super administrator privileges over content, users, and configuration.
Affected Products
- FlyCms content management system through commit edfdf724c3b944310f60c29aa755d03a00a75837
- Default installations seeded with the flycms_20260928_093335.sql database script
- Any deployment that retains the pre-provisioned flycms super administrator account
Discovery Timeline
- 2026-10-19 - CVE-2026-112296 published to the National Vulnerability Database
- 2026-10-19 - CVE-2026-112296 last modified in NVD
Technical Details for CVE-2026-112296
Vulnerability Analysis
FlyCms provisions a built-in super administrator account during installation. The SQL seeding script flycms_20260928_093335.sql creates a user named flycms with the password admin123 and the highest privilege role. These credentials are documented in the project README and are not forced to rotate on first login.
The authentication endpoint POST /api/auth/login validates the submitted credentials and a static image captcha. No additional verification, rate limiting, IP restriction, or forced password reset gates the account. Once authenticated, the attacker receives a session or token bearing full administrative privileges.
From that session, an attacker can modify published content, create or escalate user accounts, change site configuration, and in most CMS deployments, upload server-side templates or plugins that lead to remote code execution on the host.
Root Cause
The root cause is a shipped-with-default-credentials design flaw tracked as CWE-1392. The deployment artifacts persist a known administrator credential pair without requiring an installer-driven password change. Administrators who follow the documented setup remain exposed unless they manually rotate the credential.
Attack Vector
Exploitation requires only network reachability to the FlyCms administrative interface. The attacker submits a JSON or form-encoded request to POST /api/auth/login containing the username flycms, the password admin123, and a value for the image captcha challenge. No prior authentication, user interaction, or privileged position is required. Internet-exposed instances can be enumerated through fingerprinting of the FlyCms login page or default routes.
See the VulnCheck FlyCms Advisory and the GitHub FlyCms Issue Tracker for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-112296
Indicators of Compromise
- Successful authentication events for the username flycms originating from unexpected or external IP addresses
- Administrative session activity, user creation, or role changes performed by the flycms account shortly after a login event
- New or modified templates, plugins, or static assets written by the super administrator account outside of change windows
- Outbound connections or webshell-like file writes correlated with flycms session activity
Detection Strategies
- Alert on any HTTP POST /api/auth/login request where the submitted username equals flycms, regardless of outcome
- Baseline authentication source geographies and user agents, and alert on deviations for the super administrator account
- Correlate login events with subsequent configuration, user, or content modification APIs to flag post-authentication abuse
Monitoring Recommendations
- Forward FlyCms web and application logs to a centralized logging platform and retain authentication events for forensic review
- Monitor the web root and template directories for unexpected file writes attributable to the FlyCms process
- Track creation of new administrator-level accounts and privilege changes initiated by the flycms account
How to Mitigate CVE-2026-112296
Immediate Actions Required
- Change the password for the built-in flycms super administrator account to a strong, unique value, or disable the account if a replacement administrator exists
- Audit all existing user accounts for unauthorized super administrator privileges and remove unknown accounts
- Restrict network access to the FlyCms administrative interface using firewall rules, VPN, or allowlisted source IP ranges
- Review web, application, and database logs for prior logins by the flycms account from untrusted sources
Patch Information
No vendor patch is referenced in the enriched CVE data at the time of publication. Operators should track the GitHub FlyCms Issue Tracker and the FlyCms repository for a fix that removes the default credential or enforces password rotation at first login. Until a patched release is available, treat credential rotation and network segmentation as the primary controls.
Workarounds
- Rotate the flycms account password immediately after installation and before exposing the application to any untrusted network
- Remove or rename the default flycms account in the database and provision a new administrator with a unique username
- Place the administrative console behind a reverse proxy that enforces additional authentication, such as mutual TLS or SSO
- Enable application-layer rate limiting on POST /api/auth/login to slow credential-based attacks
# Example: rotate the default FlyCms super administrator password in MySQL
# Replace <NEW_BCRYPT_HASH> with a hash generated using the algorithm FlyCms expects
mysql -u root -p flycms -e \
"UPDATE sys_user SET password='<NEW_BCRYPT_HASH>' WHERE username='flycms';"
# Optional: restrict the administrative endpoint to an internal network
# nginx snippet
# location /api/auth/login {
# allow 10.0.0.0/8;
# deny all;
# proxy_pass http://flycms_backend;
# }
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

