CVE-2024-0729 is a medium severity flaw in ForU CMS up to the 2020-06-23 version, scored 5.5 by NVD. No fixed version is confirmed in the sources I could check, so limit who can reach it, watch for a vendor release, and plan an upgrade or replacement.
What's affected
The record lists ForU CMS up to the 2020-06-23 version as affected. The record says the a_name argument in cms_admin.php leads to SQL injection. The vector shows adjacent network access and a low privilege account. The CVSS vector is CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The weakness is CWE-89.
The record's description is short and does not name a fixed release. The linked pages are public write-ups of the issue, not a vendor patch notice.
How to check if you're exposed
Find ForU CMS installs and check the release date. Anything up to 2020-06-23 is in scope. Review web server logs for unusual requests to cms_admin.php, and confirm the admin area is not reachable from the public internet.
If the product reached you inside another package, run the free in-browser dependency scan at gold.safeguard.sh/scan against your manifests to see whether it appears. For standalone software, the inventory is the check: find where it is installed, which version it is, and whether the service is reachable from outside the machine.
What to do now
- Find every installation of the product and note its version.
- Check the vendor site and project repository for a newer release, and read its notes before upgrading. Do not assume a later version is fixed without a statement that says so.
- Restrict network access to the service with firewall rules so only trusted hosts can reach it.
- Watch logs for repeated odd requests or unexpected crashes aimed at the affected component.
- If the software looks unmaintained, plan to replace it, and record the risk decision in the meantime.
Why it matters
SQL injection happens when user supplied text is placed into a database query without being kept separate from the query structure. The record names the vulnerable parameter and file, and the CWE-89 tag confirms the class. The usual cure is prepared statements with bound parameters, plus least privilege database accounts so that a flaw exposes less.
The score is medium because the record rates impact as low across confidentiality, integrity and availability, and in some cases a login is required. That is a floor, not a ceiling: what an injection can read or change depends on the database account the application uses and the data behind it. Small PHP applications often connect as a powerful database user, which makes a flaw worth more than the score suggests.
The record notes that an exploit has been disclosed publicly. That is not the same as confirmed attacks, and the record does not flag this CVE in the CISA Known Exploited Vulnerabilities list. Public detail still lowers the effort for someone to try it, which is a reason to reduce exposure early.
Quick check
Is it reachable from the internet?
The vector says adjacent network, so the record describes access from the same network segment. Check your own exposure anyway.
Is there a related CVE?
Yes, CVE-2024-0728 is a file inclusion flaw in channel.php of the same product.
Sources
Last reviewed: 19 October 2026.
