CVE-2024-12901
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 was found in FoxCMS up to 1.2. Affected by this vulnerability is an unknown functionality of the file /app/api/controller/Site.php of the component API Endpoint. The manipulation of the argument password leads to improper authorization. The attack can be launched 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 confidenceFoxCMS up to version 1.2 contains an improper authorization vulnerability in the /app/api/controller/Site.php API endpoint. The application fails to properly validate the password argument during authentication, allowing remote attackers to bypass authorization controls through manipulation of this parameter.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 FoxCMS installation and versionLocate the CMS installation directory and check for version information in configuration files, typically found in a version.php file or README within the FoxCMS root directory. Compare the installed version to the affected range (<= 1.2).Affected if The installed FoxCMS version is 1.2 or lower.
-
Verify the vulnerable Site.php file existsCheck for the presence of the file /app/api/controller/Site.php in the web root. This file contains the affected API endpoint.Affected if The file /app/api/controller/Site.php exists in the installation.
-
Determine if the API endpoint is exposedCheck if the /app/api/controller/ path is accessible from the web. Inspect the web server configuration and .htaccess rules to see if direct access to the API controller directory is permitted.Affected if The API endpoint at /app/api/controller/Site.php is reachable over HTTP/HTTPS from the network.
-
Inspect password validation logic in Site.phpExamine the source code of /app/api/controller/Site.php and locate the authentication function that processes the password argument. Look for any logic that fails to properly validate the password parameter before granting access.Affected if The code shows weak or missing password validation logic before authentication decisions.
A user is affected if they run FoxCMS version 1.2 or lower with the /app/api/controller/Site.php API endpoint accessible and the password validation logic insufficiently checks the password argument.
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 dataRestrict network access to the affected API endpoint pending a vendor patch. Implement proper server-side password validation and session authentication checks in the Site.php controller. If no vendor patch is available, audit the authentication logic and enforce role-based access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12901 — 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-12901 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