CVE-2025-7478
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, which was classified as critical, was found in code-projects Modern Bag 1.0. Affected is an unknown function of the file /admin/category-list.php. The manipulation of the argument idCate leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public 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 confidenceA SQL injection vulnerability exists in the /admin/category-list.php file of Modern Bag 1.0. The idCate parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. With a CVSS score of 9.8, this critical flaw could allow complete database compromise, including data exfiltration or 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.
-
Confirm Modern Bag 1.0 is installedInspect the web application directory for files from Code Projects Modern Bag version 1.0. Look for version identifiers in any README, composer.json, or config files, or check the application footer/meta for version information.Affected if The installed application is Code Projects Modern Bag version 1.0
-
Locate the vulnerable scriptCheck if the file /admin/category-list.php exists in the web root. This file is part of the admin panel functionality.Affected if The file /admin/category-list.php is present on the server
-
Verify admin panel is accessibleAttempt to access the /admin/ directory via HTTP/HTTPS to determine if the administrative interface is reachable. This may require authentication, but the presence of the endpoint is the key factor.Affected if The /admin/ directory is accessible (with or without authentication)
-
Inspect idCate parameter handlingReview the source code of /admin/category-list.php and search for usage of the idCate parameter. Check whether this parameter is directly incorporated into SQL queries without using prepared statements, parameter binding, or input sanitization functions.Affected if The idCate parameter is used in dynamic SQL queries without parameterized query implementation or input validation
A user is affected if they have Modern Bag 1.0 installed with the /admin/category-list.php file present and the idCate parameter is processed in SQL queries without prepared statements or sanitization.
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 for the idCate parameter. Implement strict input validation, apply principle of least privilege to database accounts, and consider adding Web Application Firewall rules as a defense-in-depth measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7478 — 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-7478 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