CVE-2025-13291
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 was found in Campcodes Supplier Management System 1.0. This affects an unknown part of the file /manufacturer/confirm_order.php. Performing a manipulation of the argument ID results in sql injection. The attack can be initiated remotely. The exploit has been made public and could 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 · high confidenceSQL injection vulnerability in Campcodes Supplier Management System 1.0 allows remote attackers to manipulate the ID parameter in /manufacturer/confirm_order.php to inject arbitrary SQL queries, potentially leading to unauthorized database access, data exfiltration, or compromise of the application.
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 the installed product is Campcodes Supplier Management SystemReview your web application's documentation, footer, or source code for the product name and version. Check the application directory structure for the presence of Campcodes-specific folders and files.Affected if The product is not Campcodes Supplier Management System version 1.0
-
Locate the vulnerable PHP fileCheck if the file /manufacturer/confirm_order.php exists in your web application root directory. Navigate to the manufacturer folder and confirm confirm_order.php is present.Affected if The file /manufacturer/confirm_order.php does not exist on the system
-
Verify the application is network-accessibleConfirm the web application is accessible over the network. Attempt to access the /manufacturer/ endpoint from a browser or curl command.Affected if The application is not accessible or the /manufacturer/ path returns a 404 error
-
Test for SQL injection vulnerability in the ID parameterSend a crafted request to /manufacturer/confirm_order.php with an ID parameter value containing SQL syntax (e.g., ID=1' OR '1'='1). Compare the response to a normal request. Look for SQL error messages, unusual database behavior, or differences in response content.Affected if The application returns SQL error messages or exhibits unexpected behavior when special characters are injected into the ID parameter
The system is affected if it runs Campcodes Supplier Management System version 1.0 with the file /manufacturer/confirm_order.php accessible over the network and the ID parameter accepts unsanitized SQL input.
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 queries (prepared statements) in confirm_order.php and conduct a broader code audit to identify and remediate similar SQL injection vulnerabilities throughout the application.
- 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-13291 — 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-13291 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