CVE-2025-15408
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 code-projects Online Guitar Store 1.0. Affected is an unknown function of the file /admin/Create_product.php. Performing a manipulation of the argument dre_title results in sql injection. The attack is possible to be carried out 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 · moderate confidenceA SQL injection vulnerability exists in the /admin/Create_product.php script of the Online Guitar Store 1.0 application. The dre_title parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. With a CVSS 9.8 rating, this critical flaw can allow unauthenticated remote attackers to execute arbitrary SQL commands, potentially leading to complete database compromise including data exfiltration or administrative 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.
-
Identify the application versionLocate any version file, README, or footer metadata that displays the application version. Compare against '1.0' for Anisha Online Guitar Store.Affected if The installed version is Anisha Online Guitar Store 1.0
-
Verify Create_product.php existsCheck if the file /admin/Create_product.php exists in the web root directory.Affected if The file exists in the application directory
-
Examine the dre_title parameter handlingOpen /admin/Create_product.php in a text editor or use 'grep -n 'dre_title' /path/to/admin/Create_product.php' to locate where the parameter is used in SQL queries without proper sanitization or prepared statements.Affected if The code directly incorporates the dre_title parameter into SQL queries without using prepared statements or escaping functions
-
Determine if admin endpoint is exposedAttempt to access http://target-site.com/admin/Create_product.php via HTTP request. If the page loads or responds, the vulnerable script is accessible.Affected if The /admin/Create_product.php endpoint is accessible without authentication or with admin credentials
You are affected if you are running Anisha Online Guitar Store version 1.0 and the /admin/Create_product.php file exists with the dre_title 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 dataImmediate remediation requires implementing parameterized queries (prepared statements) for all database interactions in Create_product.php, validating/sanitizing all user inputs, and temporarily disabling the affected functionality until a patch is applied. Consider reviewing all admin-facing PHP files for similar injection vulnerabilities.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15408 — 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-15408 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