CVE-2022-2750
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 SourceCodester Company Website CMS. Affected is an unknown function of the file /dashboard/add-service.php of the component Add Service Handler. The manipulation leads to unrestricted upload. It is possible to launch the attack remotely. VDB-206022 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 · high confidenceUnrestricted file upload vulnerability in SourceCodester Company Website CMS's /dashboard/add-service.php Add Service Handler allows remote attackers to upload arbitrary files, likely including malicious PHP scripts, due to missing file type validation and sanitization.
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 dataall versionsCVSS 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.
-
Locate the Company Website CMS installationSearch the web server document root for files named 'add-service.php' or directories containing 'Company Website CMS' or 'company_website' in the path. Common locations: /var/www/html/, /htdocs/, C:\inetpub\wwwroot\Affected if The CMS is installed and the vulnerable add-service.php file exists in the /dashboard/ directory under the web root
-
Verify the vulnerable script existsCheck for the presence of /dashboard/add-service.php in the web root. This is the specific file that handles the Add Service functionality and lacks file type validation.Affected if The file /dashboard/add-service.php exists in the web-accessible directory
-
Confirm upload functionality is accessibleAccess the URL path /dashboard/ in a web browser or via curl to verify the dashboard is accessible. The add-service.php handler processes file uploads when the Add Service feature is used.Affected if The dashboard directory is web-accessible without authentication or with low-privileged user authentication
-
Check PHP file upload configurationReview php.ini for 'file_uploads = On' setting. Also check if the web server user (www-data, apache, etc.) has write permissions to any upload directories configured in the application.Affected if PHP file uploads are enabled (file_uploads=1 in php.ini) and the application has write access to upload directories
-
Identify uploaded file storage locationExamine the application code in add-service.php or related files to determine where uploaded files are stored. Check if these files are stored within the web root and retain their original extensions.Affected if Uploaded files are saved inside the web-accessible directory (web root) without renaming or extension modification, allowing executable files like .php to be accessed directly
A user is affected if Company Website CMS is installed with the /dashboard/add-service.php file accessible on the web server and PHP file uploads are enabled, allowing unauthenticated or low-privileged attackers to upload and execute malicious files.
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 allowlist-based file type validation, verify file content (magic bytes), rename uploaded files, and store uploads outside the webroot or with executable permissions disabled.
- 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-2022-2750 — 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-2022-2750 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