CVE-2023-7147
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 gopeak MasterLab up to 3.3.10. Affected is the function base64ImageContent of the file app/ctrl/User.php. The manipulation of the argument image leads to unrestricted upload. It is possible to launch the attack remotely. VDB-249150 is the identifier 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 · moderate confidenceThe base64ImageContent function in MasterLab's User.php accepts base64-encoded image data without proper validation, allowing attackers to upload arbitrary files (including executable scripts) to the server. This unrestricted upload vulnerability is exploitable remotely with no authentication mentioned, earning the critical 9.8 CVSS score.
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 versionLocate the version file or header in your MasterLab installation (commonly in composer.json, package.json, or a VERSION file in the root directory). Compare the version number to the affected range: <= 3.3.10.Affected if The installed version is 3.3.10 or lower.
-
Locate the vulnerable functionFind the file app/vendor/masterlab/src/User.php (or similar path under src/). Search for the function named 'base64ImageContent' and inspect its implementation.Affected if The function exists and contains base64_decode logic without file type validation.
-
Inspect validation logic in the upload handlerExamine the base64ImageContent function for any validation of the decoded data. Look for checks on file extensions, MIME types, or magic bytes before the file is saved.Affected if No validation or only superficial extension checking (e.g., only checking file extension string) is present.
-
Identify file storage locationDetermine where uploaded base64 images are saved by examining the function's file write operations. Check if uploads are stored within the webroot or in a publicly accessible directory.Affected if Uploaded files are stored in a web-accessible directory with their original or predictable filenames.
-
Verify upload endpoint accessibilityDetermine if the upload functionality in User.php is reachable without authentication by checking the surrounding controller code and routing configuration.Affected if The endpoint can be accessed without valid authentication credentials.
You are affected if your MasterLab version is 3.3.10 or lower AND the base64ImageContent function in User.php lacks proper validation AND uploaded files are stored in a web-accessible location.
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 strict file type validation (magic bytes, MIME type checking) before processing base64 image content, restrict uploaded files to safe extensions (jpg, png, gif), store uploads outside the webroot or with non-executable permissions, and add authentication checks to the upload endpoint.
- 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-2023-7147 — 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-7147 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