CVE-2025-14529
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 flaw has been found in Campcodes Retro Basketball Shoes Online Store 1.0. The affected element is an unknown function of the file /admin/admin_running.php. This manipulation of the argument pid causes sql injection. It is possible to initiate the attack remotely. The exploit has been published 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 Campcodes Retro Basketball Shoes Online Store 1.0 allows remote attackers to inject malicious SQL queries via the 'pid' parameter in /admin/admin_running.php. The lack of input sanitization or parameterized queries on this parameter enables database manipulation.
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.
-
Locate the vulnerable PHP fileSearch for the file admin_running.php in the web application's directory structure, typically under /admin/ pathAffected if The file admin_running.php exists in the application root or admin directory
-
Verify the application versionCheck the application's version information (often in a README, about page, or version constant in source files) and confirm it is version 1.0Affected if The installed version is Campcodes Retro Basketball Shoes Online Store 1.0
-
Examine the pid parameter handling in the vulnerable fileOpen admin_running.php and inspect the code around line where the 'pid' parameter is used in SQL queries without proper sanitization or parameterized queriesAffected if The code uses the 'pid' parameter directly in SQL queries (e.g., SELECT * FROM table WHERE pid='$pid') without using prepared statements or escaping functions
-
Check if the admin panel is accessibleAttempt to access the /admin/ directory or admin_running.php through the web server to determine if the vulnerable endpoint is exposedAffected if The admin interface and admin_running.php are accessible without authentication or with valid admin credentials
-
Identify SQL injection entry pointReview the PHP code in admin_running.php to confirm the 'pid' parameter from GET or POST requests is inserted directly into SQL statements without sanitizationAffected if The 'pid' parameter is obtained from $_GET['pid'] or $_POST['pid'] and concatenated directly into SQL queries
The environment is affected if running Campcodes Retro Basketball Shoes Online Store version 1.0 with the admin_running.php file present and the 'pid' parameter being used in unsanitized SQL queries.
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 dataImplement prepared statements/parameterized queries for the 'pid' parameter in admin_running.php, and apply input validation and output encoding. Consider deploying a WAF as an interim measure until the code fix is applied.
- 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-14529 — 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-14529 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