CVE-2024-47487
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 · uneditedThere is a SQL injection vulnerability in some HikCentral Professional versions. This could allow an authenticated user to execute arbitrary SQL queries.
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 HikCentral Professional allowing authenticated users to execute arbitrary SQL queries. The vulnerability exists in certain versions of the product and is exploitable by users with valid authentication credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.0, < 2.6.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed HikCentral Professional versionAccess the HikCentral Professional admin console or check system information panel. The version is typically visible in the About or System Info section of the management interface, or can be retrieved via the system's built-in version check command if available.Affected if Version number is >= 2.0.0 and < 2.6.1
-
Confirm HikCentral Professional is deployedVerify that the target system is running HikCentral Professional (not another Hikvision product). Check installed applications or services list for 'HikCentral Professional' or 'HikCentral' with Professional designation.Affected if The software identified is HikCentral Professional version 2.0.0 through 2.5.x
-
Determine if web interface or API is accessibleCheck if the HikCentral Professional web interface or API endpoints are exposed and reachable. This is the attack vector for the SQL injection.Affected if Web interface or API is accessible to authenticated users (the vulnerability requires authentication to exploit)
If HikCentral Professional version is 2.0.0 or higher but below 2.6.1 and the web interface is accessible, the environment is affected by this SQL injection vulnerability.
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.
dbcve · scoped2.6.1
Apply vendor-supplied patches or upgrade to a patched version of HikCentral Professional. As an interim control, review and restrict database query permissions for authenticated user accounts.
2.6.1
- Download HikCentral Professional version 2.6.1 or later from the official Hikvision website
- Back up the current HikCentral Professional configuration and database
- Install the version 2.6.1 update following Hikvision's standard upgrade procedure
- Verify the upgrade was successful by checking the software version
- Confirm the SQL injection vulnerability is remediated by testing with the authenticated user context
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47487 — 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-2024-47487 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