CVE-2025-65336
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 · uneditedEcommerce-project-with-php-and-mysqli-Fruits-Bazar 1.0 is vulnerable to SQL Injection in /show_price_by_pdtId.php.
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 the show_price_by_pdtId.php file of the Fruits-Bazar e-commerce application. The pdtId parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL statements. This could enable unauthorized database access, data exfiltration, or potential remote code execution depending on database configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 Fruits-Bazar application installationSearch the web server document root for directories containing 'Fruits-Bazar', 'fruits', or 'bazar' in the name. Check common paths like /var/www/html/, /www/, /home/*/public_html/, or C:\inetpub\wwwroot\Affected if The Fruits-Bazar application directory exists on the server
-
Confirm application version is v1.0Look for a version file (version.txt, ver.php, README) in the Fruits-Bazar directory, or check the main index.php for a hardcoded version string. Compare the found version against the affected v1.0Affected if The installed version is exactly v1.0
-
Verify show_price_by_pdtId.php existsLocate the file show_price_by_pdtId.php within the Fruits-Bazar installation directory structure, typically under /admin/, /includes/, or the root folderAffected if The file show_price_by_pdtId.php is present in the installation
-
Check if application is accessible and runningAttempt to access the application's main page via HTTP/HTTPS to confirm the server is hosting the vulnerable v1.0 instanceAffected if The Fruits-Bazar v1.0 application responds to HTTP requests, indicating active deployment
-
Inspect vulnerable code pattern in show_price_by_pdtId.phpOpen show_price_by_pdtId.php and search for SQL query patterns using $_GET, $_POST, or $_REQUEST directly concatenated into queries without prepare() or parameterized bindingAffected if Direct parameter interpolation into SQL queries is found without input sanitization or prepared statements
If Fruits-Bazar v1.0 is deployed, the file show_price_by_pdtId.php exists, and SQL queries in that file use unsanitized user input directly, the environment is affected by CVE-2025-65336.
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 query construction with prepared statements using MySQLi prepared statements ($mysqli->prepare), ensuring all user input is bound as parameters rather than concatenated directly into queries. Validate and sanitize all inputs according to whitelist approaches.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65336 — 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-65336 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