CVE-2025-9726
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 security flaw has been discovered in Campcodes Farm Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /review.php. The manipulation of the argument pid results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be exploited.
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 confidenceSQL injection vulnerability in Campcodes Farm Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the unprotected pid parameter in /review.php. The critical CVSS 9.8 score indicates complete compromise potential with no authentication required.
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.0CVSS 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.
-
Confirm Campcodes Farm Management System versionLocate the application directory and check version files (such as README, version.php, or admin dashboard About section). Compare the installed version to the affected range (1.0).Affected if The installed version is exactly 1.0 or falls within the affected version range.
-
Verify /review.php exists in webrootCheck the application web directory for the presence of review.php file. Common paths include /review.php or /modules/reviews/review.php.Affected if The file /review.php exists and is accessible via the web server.
-
Inspect the pid parameter handling in review.phpOpen /review.php in a text editor or use 'grep -n 'pid' /path/to/review.php' to locate where the 'pid' parameter is processed. Look for SQL queries that incorporate this parameter without prepared statements or parameter binding.Affected if The code contains SQL queries that directly include the 'pid' parameter from $_GET or $_REQUEST without sanitization or parameterized queries.
-
Test pid parameter for SQL injection vulnerability (safe test)Send a benign SQL injection test payload to the endpoint such as '?pid=1' (baseline), then '?pid=1' (with a trailing quote '?pid=1'') to observe if the application returns a database error. Use a local test or controlled request, not against production without authorization.Affected if The application returns different responses between baseline and quoted input, or displays SQL error messages indicating unsanitized input is being processed.
You are affected if you are running Campcodes Farm Management System version 1.0 and the /review.php file processes the 'pid' parameter without parameterized queries or input sanitization.
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 dataReplace dynamic SQL queries with parameterized statements/prepared statements in review.php. Audit the entire application for additional SQL injection vulnerabilities and apply vendor patches immediately.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9726 — 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-9726 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