CVE-2026-5563
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in AutohomeCorp frostmourne up to 1.0. Affected is the function httpTest of the file /api/monitor-api/alarm/previewData of the component Alarm Preview. The manipulation results in sql injection. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the httpTest function of the Alarm Preview component at endpoint /api/monitor-api/alarm/previewData in AutohomeCorp frostmourne up to v1.0. Remote attackers can exploit unsanitized user input to inject malicious SQL queries through this API endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if frostmourne is installedCheck for the presence of the frostmourne application or search for files/directories named 'frostmourne' in the system. Look for application directories, container images, or deployment manifests.Affected if The frostmourne application from AutohomeCorp is found in the environment
-
Determine the installed version of frostmourneCheck the application's version information. This may be in a version file, pom.xml, package.json, Docker image tag, or application startup logs. Compare against '1.0' as the upper bound of affected versions.Affected if The installed version is 1.0 or any earlier version
-
Verify the vulnerable API endpoint is exposedCheck if the application exposes HTTP endpoints. Look for API documentation, swagger/OpenAPI specs, or network configuration that shows whether /api/monitor-api/alarm/previewData is accessible.Affected if The /api/monitor-api/alarm/previewData endpoint is exposed and reachable
-
Confirm the Alarm Preview component is enabledCheck the application configuration to determine if the monitor-api module and Alarm Preview feature are enabled. This may be in configuration files, database records, or feature flags.Affected if The Alarm Preview component (monitor-api/alarm/previewData) is enabled and operational
If frostmourne version 1.0 or earlier is installed with the /api/monitor-api/alarm/previewData endpoint exposed and the Alarm Preview component enabled, the environment is vulnerable to CVE-2026-5563.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries or prepared statements for all database operations, apply input validation and sanitization on the /api/monitor-api/alarm/previewData endpoint, and ensure database accounts used by the application follow least privilege principles.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5563 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5563 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data