CVE-2025-7514
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 Modern Bag 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/contact-list.php. The manipulation of the argument idStatus leads to sql injection. The attack may be launched 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 · high confidenceSQL injection vulnerability in Modern Bag 1.0's /admin/contact-list.php allows remote attackers to inject malicious SQL queries via the idStatus parameter. The lack of input sanitization or parameterized queries enables unauthenticated SQL injection attacks with critical severity (CVSS 9.8).
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 installedLocate the Modern Bag application files on the server. Check for the presence of /admin/contact-list.php or search for files containing 'Modern Bag' or version indicators.Affected if The application folder contains Modern Bag version 1.0
-
Verify the vulnerable endpoint existsCheck if /admin/contact-list.php file exists in the web root or admin directory of the Modern Bag installation.Affected if The file contact-list.php exists in the /admin/ directory
-
Inspect the contact-list.php code for SQL injection vulnerabilityOpen contact-list.php and search for the idStatus parameter usage. Look for SQL queries that directly incorporate $_GET['idStatus'] or $_POST['idStatus'] without using prepared statements, parameter binding, or input sanitization.Affected if The code contains unsanitized direct insertion of idStatus into SQL queries (e.g., "SELECT ... WHERE idStatus = " . $_GET['idStatus'])
-
Check if the admin interface is network-accessibleDetermine if the /admin/ endpoint is exposed to the network or internet without proper access controls. Attempt to access the contact-list.php endpoint remotely.Affected if The /admin/contact-list.php endpoint is reachable from an untrusted network
A user is affected if Modern Bag 1.0 is installed, the contact-list.php file exists, and the idStatus parameter is used in SQL queries without parameterized queries or input 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 prepared statements/parameterized queries and implement proper input validation on the idStatus parameter. Apply immediate input sanitization as an interim measure until the code fix is deployed.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7514 — 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-7514 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