CVE-2023-7144
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 classified as critical has been found in gopeak MasterLab up to 3.3.10. This affects the function sqlInject of the file app/ctrl/framework/Feature.php of the component HTTP POST Request Handler. The manipulation of the argument pwd leads to sql injection. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-249147.
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 confidenceSQL injection vulnerability in gopeak MasterLab's Feature.php file allows remote attackers to inject malicious SQL queries via the 'pwd' parameter in HTTP POST requests to the sqlInject function. The lack of parameterized queries or proper input sanitization enables complete database compromise.
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 application files and check the version declaration in the main configuration or version file (commonly version.php, composer.json, or a similar version indicator within the MasterLab installation directory).Affected if The installed version is 3.3.10 or lower.
-
Locate the vulnerable Feature.php fileSearch for the Feature.php file within the MasterLab source code directory structure, typically found in the application or src folder.Affected if The Feature.php file exists in the MasterLab installation.
-
Verify the sqlInject function existsOpen Feature.php and search for the function definition 'function sqlInject' to confirm the vulnerable function is present in the codebase.Affected if The sqlInject function is defined in Feature.php.
-
Confirm POST parameter handling for pwdInspect the sqlInject function code to verify it processes a 'pwd' parameter from HTTP POST requests without proper sanitization or parameterized queries.Affected if The function accepts the 'pwd' POST parameter and uses it directly in SQL queries without prepared statements or input validation.
-
Check application accessibilityDetermine if the affected endpoint is accessible over the network by reviewing application routing and access controls.Affected if The sqlInject function is exposed via an accessible HTTP endpoint that accepts POST requests.
A user is affected if MasterLab version 3.3.10 or lower is installed, the Feature.php file with the sqlInject function exists, and the pwd parameter handling lacks parameterized 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 dataImplement prepared statements/parameterized queries to neutralize SQL injection vectors, validate and sanitize all user inputs, and upgrade to version 3.3.11 or later if a patched release is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7144 — 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-7144 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