CVE-2024-1254 is a medium severity SQL injection in the Byzoro Smart S20 Management Platform, up to the 20231120 release. NVD scores it 4.7 and the record says exploit details are public. The vendor did not respond, so no fix is confirmed.
What's affected
The record names Byzoro Smart S20 Management Platform, up to the 20231120 release. The weak spot is the file sysmanage/sysmanageajax.php, with the id argument. The remote attack path and the public disclosure both come from the VulDB entry, number 252993, which the record paraphrases.
NVD scores it 4.7, which is Medium. The vector requires high privileges, so an attacker needs a strong foothold first, which explains the 4.7 score.
No fixed version is stated and the record says the vendor did not respond. Ask the vendor for a patched release and keep the device away from untrusted networks.
The related CVE-2024-1253 covers the Smart S40, a different model from the same vendor, so check every Byzoro appliance you run.
Weakness class: CWE-89. The NVD record carries the vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L and a score of 4.7.
How to check if you're exposed
Look for the file named in the record, the file sysmanage/sysmanageajax.php, and review how it builds its SQL. If you cannot read the code, check web logs for requests to that path with unusual values in the id parameter.
If you are not sure whether the product is installed, search your server inventory and application list for its name, since small business software like this often sits on a single forgotten host.
Safeguard has a free in-browser dependency scan at gold.safeguard.sh/scan for the libraries in your own projects, and reachability analysis helps you tell which findings your code actually calls.
What to do now
- Find every installation of Byzoro Smart S20 Management Platform and record the version.
- Ask the vendor for a patched release and apply it as soon as it is available.
- Until a fix exists, limit who can reach the application, for example by placing it behind a VPN or an allow list, and block public access to the file sysmanage/sysmanageajax.php.
- Watch web server logs for requests to the affected route and for new or changed files.
- Plan a move to a maintained product if the vendor does not respond.
Why it matters
SQL injection (CWE-89) means the value of the id argument ends up inside a database query as text, so crafted input can change what the query does. The standard fix is parameterised queries, where the database treats input strictly as data.
Depending on the database account the application uses, the outcome can be reading, changing or deleting records. The record does not describe the exact impact, and I have not tested the product, so the lowered score reflects the vector and not a worst case. The record says the vendor was contacted early and did not respond in any way.
Quick check
Is CVE-2024-1254 known to be exploited?
The KEV flag in the record is false. The record does say the exploit details have been disclosed publicly, so do not wait for exploitation reports before acting.
Where can I read the original report?
The record cites VulDB entry 252993 and an outside write up. I could not retrieve them, so check them yourself for the proof of concept level detail, which this post leaves out on purpose.
Sources
Last reviewed: 19 October 2026.
