CVE-2025-66802
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 · uneditedSourcecodester Covid-19 Contact Tracing System 1.0 is vulnerable to RCE (Remote Code Execution). The application receives a reverse shell (php) into imagem of the user enabling RCE.
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 confidenceSourcecodester Covid-19 Contact Tracing System 1.0 contains an insecure file upload vulnerability that allows attackers to upload malicious PHP files disguised as user profile images. The application does not properly validate file types and contents, enabling arbitrary code execution on the server.
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 Covid-19 Contact Tracing System installationLook for the application in your web server's document root. Check for directories or files related to 'contact tracing', 'covid', or the project name. Inspect web server access logs for requests to typical entry points like index.php or login pages.Affected if The application Covid-19 Contact Tracing System version 1.0 is present on the server
-
Verify the installed versionCheck the application's source code for a version identifier. Common locations include: a version.php file, a config file, the main index.php header comment, or a changelog/readme file. Compare the version number to 1.0.Affected if The installed version is exactly 1.0
-
Locate the file upload functionalitySearch the application source code for file upload forms. Look for HTML forms with 'enctype="multipart/form-data"' or PHP code handling $_FILES superglobal. Identify the upload handler script and the directory where uploads are stored.Affected if A file upload feature exists and accepts user-submitted files
-
Determine if uploads are stored in webrootExamine the upload directory path in the code. Check if the directory where uploaded files are saved is accessible via HTTP/HTTPS (is inside the web document root). Common upload paths like 'uploads/', 'images/', or 'assets/' are typically web-accessible.Affected if Uploaded files are stored in a directory accessible via the web server
-
Check for file type validationReview the upload handling code for server-side validation. Look for checks on file extensions ($_FILES['name']), MIME types, or file content validation (getimagesize). Determine if the validation uses an allowlist or only relies on client-side checks or extension renaming.Affected if No server-side allowlist validation is performed, or validation can be bypassed
-
Verify PHP execution is allowed in upload directoryCheck the web server configuration (Apache .htaccess, Nginx config) for the upload directory. Look for 'AllowOverride All' or lack of 'php_flag engine off' or 'deny from all' directives that would prevent PHP execution.Affected if PHP files can be executed when accessed through the web server in the upload directory
If the Covid-19 Contact Tracing System 1.0 is installed with its file upload functionality exposed via the web and without proper server-side validation or PHP execution restrictions, the system is vulnerable to remote code execution via malicious file upload.
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 upload validation: verify actual file content (magic bytes) rather than trusting file extensions, store uploads outside web root, disable PHP execution in upload directories, and whitelist allowed file types (images only with verified MIME types).
- Consultation3.0 h
- Implementation5.0 h
- Testing4.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66802 — 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-66802 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