CVE-2023-7146
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, has been found in gopeak MasterLab up to 3.3.10. This issue affects the function sqlInjectDelete of the file app/ctrl/framework/Feature.php of the component HTTP POST Request Handler. The manipulation of the argument phone leads to sql injection. The exploit has been disclosed to the public and may be used. The identifier VDB-249149 was assigned to this vulnerability.
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 gopeak MasterLab's Feature.php allows injection via the phone parameter in HTTP POST requests to the sqlInjectDelete function. The lack of proper input sanitization or parameterized queries enables attackers to manipulate SQL queries.
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<= 3.3.10CVSS 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 MasterLab installation and versionLocate the MasterLab installation directory and check the version file (typically version.php, package.json, or similar version manifest). Compare the installed version to the affected range: <= 3.3.10Affected if The installed version is 3.3.10 or lower
-
Locate vulnerable Feature.php fileFind the Feature.php file within the MasterLab application directory structure, typically under src/, app/, or includes/ pathsAffected if The file exists in the installation
-
Verify sqlInjectDelete function presenceOpen Feature.php and search for the function definition 'function sqlInjectDelete' or 'function sqlInjectDelete('Affected if The function exists in Feature.php
-
Inspect phone parameter handlingWithin the sqlInjectDelete function, examine how the 'phone' parameter from HTTP POST requests is used in SQL queries. Look for direct string concatenation or lack of parameterized queriesAffected if The phone parameter is used in SQL queries without prepared statements or proper escaping
-
Confirm POST endpoint accessibilityCheck if the Feature.php file or its containing route is accessible via HTTP POST method to the sqlInjectDelete functionAffected if The endpoint accepts POST requests with the phone parameter
A user is affected if they are running MasterLab version 3.3.10 or lower, the vulnerable Feature.php file with the sqlInjectDelete function exists, and the phone parameter is used in unsanitized SQL queries accessible via POST requests.
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 all database operations in the affected function and validate/sanitize the phone parameter input. Conduct a broader code review to identify similar SQL injection vulnerabilities.
- 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-2023-7146 — 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-2023-7146 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