CVE-2025-29181
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 · uneditedFOXCMS <= V1.25 is vulnerable to SQL Injection via $param['title'] in /admin/util/Field.php.
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 · high confidenceFOXCMS versions 1.25 and prior contain a SQL injection vulnerability in /admin/util/Field.php where the $param['title'] parameter is not properly sanitized before being used in database queries, allowing authenticated attackers to inject malicious SQL code.
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.25CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Foxcms installation and versionLocate the Foxcms installation directory and check the version indicator (such as a version file, composer.json, or admin dashboard version display). Compare the installed version to the affected range: versions 1.25 and prior.Affected if The installed Foxcms version is 1.25 or lower.
-
Verify vulnerable file existsCheck for the presence of the file /admin/util/Field.php in the Foxcms installation directory.Affected if The file /admin/util/Field.php exists in the installation.
-
Confirm admin access is availableDetermine whether the administrative interface is accessible. This may involve checking if /admin/ routes are enabled, if admin accounts exist, and if the login page responds.Affected if Administrative access to Foxcms is possible or configured.
-
Inspect Field.php for vulnerable code patternExamine the code in /admin/util/Field.php. Look for database query code that uses the $param['title'] variable without proper sanitization, prepared statements, or parameterized queries.Affected if The code in Field.php contains SQL queries using $param['title'] without sanitization or parameterization.
-
Check for indicators of exploitationReview web server logs and application audit logs for suspicious SQL patterns in requests to admin/util/Field.php, particularly in title parameters.Affected if Log analysis reveals SQL injection attempts or successful exploit indicators targeting the title parameter.
If Foxcms version 1.25 or prior is installed, the admin interface is accessible, and Field.php contains unsanitized $param['title'] usage in SQL queries, the environment is affected by this SQL injection vulnerability.
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 dataUpgrade to a patched version of FOXCMS after V1.25. If no patch is available, implement prepared statements or parameterized queries for the title parameter in Field.php and conduct a broader code audit for similar injection points.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29181 — 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-2025-29181 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