CVE-2024-0890 is a medium severity flaw (CVSS 6.3) in hongmaple octopus. The record says the product uses continuous delivery with rolling releases, so no affected or fixed version details are available. This guide covers who is affected, how to check your exposure, and what to do now.
What's affected
hongmaple octopus 1.0, the file /system/dept/edit, argument ancestors.
The record gives a CVSS base score of 6.3 (Medium), vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The weakness class is CWE-89.
The record says the argument named ancestors in the department edit function is passed into a query in an unsafe way. A write-up is linked in the references and the record says the exploit has been disclosed publicly.
The record says exploit details have been disclosed publicly, so assume that attackers can learn how the weakness works. The record says the product uses continuous delivery with rolling releases, so no affected or fixed version details are available. Compare your deployment against the current repository.
How to check if you're exposed
Check the commit or build you deployed against the project repository. Search your access logs for requests to /system/dept/edit from unexpected sources.
A free in-browser dependency scan at gold.safeguard.sh/scan can show whether a software package in your own projects matches this CVE, and the Gold directory entry for CVE-2024-0890 keeps the record details in one place. Reachability analysis helps you separate installations where the vulnerable code can actually be hit from those where it sits unused.
For hardware and appliances, no scanner will find them unless they are in an inventory, so start with a list of every device and application of this kind on your network.
What to do now
- Identify every instance of hongmaple octopus in your environment, including test and forgotten systems.
- Compare the version you found with the affected range above.
- Look for a fixed release from the vendor or project. The record says the product uses continuous delivery with rolling releases, so no affected or fixed version details are available.
- Apply mitigations while you wait: limit access to the admin area, put a filtering layer in front of it, and move query construction to parameterized statements if you maintain a fork.
- Review logs around the affected component for unusual requests.
- Record the decision and a re-check date in your vulnerability tracker.
Why it matters
The weakness is SQL injection, CWE-89. The application builds a database query from a request value without separating data from the query text, so a crafted value can change what the query does. The usual outcomes are reading rows the caller should not see, changing data, or in some setups going further.
The fix pattern is well known: parameterized queries, input validation on fields such as sort keys, and least privilege on the database account the application uses. Applications that never received a vendor fix need those controls added around them, for example at a web application firewall or by restricting who can reach the page.
The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog, and none of the pages used for this article report exploitation in the wild.
Quick check
What is the lasting fix for this class of bug?
Use parameterized queries and validate fields such as sort keys against a fixed list.
Where can I confirm the fixed version?
Check the vendor or project advisory first. The record says the product uses continuous delivery with rolling releases, so no affected or fixed version details are available. This article is based on the NVD record and the pages listed under Sources.
Sources
- https://github.com/biantaibao/octopus_SQL2/blob/main/report.md
- https://vuldb.com/?ctiid.252042
- https://vuldb.com/?id.252042
- Safeguard Gold record for CVE-2024-0890
Last reviewed: 19 October 2026.
