CVE-2025-12338
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 weakness has been identified in Campcodes Retro Basketball Shoes Online Store 1.0. This vulnerability affects unknown code of the file /admin/admin_product.ph. Executing a manipulation of the argument pid can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.
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 Retro Basketball Shoes Online Store 1.0 allows remote attackers to inject malicious SQL queries via the 'pid' parameter in the /admin/admin_product.php file. With a CVSS score of 9.8 and publicly available exploits, this critical flaw enables complete database compromise including data exfiltration and potential system takeover.
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 product and versionLocate and identify the Campcodes Retro Basketball Shoes Online Store installation. Check for version indication in the application, such as in the admin panel, about page, or any version file. Compare your installed version to the affected version 1.0.Affected if The installed version is 1.0 or if version cannot be determined but the product matches.
-
Locate vulnerable fileSearch for the admin_product.php file within the application web root, typically under a /admin/ directory path.Affected if The file /admin/admin_product.php exists in the installation.
-
Inspect pid parameter handlingExamine the admin_product.php file source code to determine how the 'pid' parameter is processed. Look for direct inclusion of the pid parameter in SQL queries without parameterized statements or proper input sanitization.Affected if The code uses the pid parameter directly in SQL queries without prepared statements, parameter binding, or evident sanitization functions.
-
Verify network accessibilityDetermine if the admin_product.php endpoint is accessible over the network. Check if the /admin/ directory requires authentication and whether the application is exposed to untrusted networks.Affected if The vulnerable endpoint is accessible remotely without requiring authentication or with weak authentication.
You are affected if you have Campcodes Retro Basketball Shoes Online Store version 1.0 installed, the admin_product.php file exists, the pid parameter is used unsafely in SQL queries, and the endpoint is network-accessible.
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 for the pid parameter in admin_product.php and audit other parameters in the application for similar injection flaws. Apply vendor patch immediately if available.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12338 — 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-12338 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