CVE-2025-9761
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 vulnerability has been detected in Campcodes Online Feeds Product Inventory System 1.0. This vulnerability affects unknown code of the file /feeds/index.php of the component Login. The manipulation of the argument Username leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed publicly 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 confidenceSQL injection vulnerability in the login form of Campcodes Online Feeds Product Inventory System 1.0 at /feeds/index.php. The Username parameter is not properly sanitized, allowing remote attackers to inject malicious SQL commands. This pre-authentication flaw with CVSS 9.8 could allow complete database compromise including data exfiltration and potential system access.
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 application presenceLocate the file /feeds/index.php in the web server document root or application directory. On Linux/Unix, use: find /var/www -name 'index.php' -path '*/feeds/*' 2>/dev/null or on Windows search for the path containing 'feeds' and 'index.php'.Affected if The file /feeds/index.php exists on the server.
-
Verify product identityExamine the application's source code or footer for version information. Check for a version.txt, README file, or within index.php for a version string like 'v1.0' or 'version 1.0'. Also check the page title or meta tags for product name.Affected if The application is identified as Campcodes Online Feeds Product Inventory System version 1.0.
-
Confirm login form accessibilityAccess the URL /feeds/index.php via HTTP/HTTPS and verify the login form loads. Use curl -I https://targetsite.com/feeds/index.php or access via browser to confirm the login page is reachable.Affected if The login form at /feeds/index.php loads without authentication required.
-
Identify vulnerable parameterView the HTML source of the login form at /feeds/index.php. Look for an input field with name='username' or similar that submits to the login processing script. The vulnerability exists in the Username parameter handling.Affected if A login form with a Username input field exists at /feeds/index.php.
If Campcodes Online Feeds Product Inventory System version 1.0 is installed and the login form at /feeds/index.php is accessible, 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 dataApply vendor patch when available; temporarily deploy WAF rules and implement proper input validation with parameterized queries for all login-related database operations.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9761 — 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-9761 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