CVE-2024-12900
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 vulnerability classified as critical has been found in FoxCMS up to 1.2. Affected is an unknown function of the file /install/installdb.php of the component Configuration File Handler. The manipulation of the argument database password leads to code injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
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 confidenceCode injection vulnerability in FoxCMS installer (installdb.php) allows remote attackers to inject arbitrary code via the database password parameter during the installation process. The vulnerable component is the Configuration File Handler which processes the password without proper sanitization.
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<= 1.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 if FoxCMS is installedCheck for the presence of FoxCMS by looking for characteristic files (e.g., index.php, config.php) or the /install/ directory in the web root. Look for FoxCMS-specific files or directories.Affected if FoxCMS is present on the system
-
Determine the FoxCMS versionCheck the version number in known version files such as version.php, config.php, or any README/CHANGELOG files in the web root. Compare the found version against the affected range (<= 1.2).Affected if The installed version is 1.2 or lower, or the version cannot be determined and the product appears to be FoxCMS
-
Verify if the /install/ directory is accessibleAttempt to access the /install/ directory via HTTP/HTTPS request to the web server. Check if the directory exists and returns a response (not a 404 error).Affected if The /install/ directory exists and is accessible via web request, indicating installation was not completed or the directory was not removed
-
Check if installdb.php exists and is accessibleRequest the installdb.php file directly via HTTP/HTTPS (e.g., /install/installdb.php) to determine if it is present and reachable.Affected if installdb.php is accessible via the web and accepts user input for the database password parameter
A user is affected if FoxCMS version 1.2 or lower is installed AND the /install/ directory (including installdb.php) remains accessible on the web server.
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 dataRemove or restrict access to the /install/ directory after installation completes. Implement proper input validation and parameterized queries for the database password field in installdb.php to prevent code injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12900 — 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-12900 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