CVE-2024-10420
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 SourceCodester Attendance and Payroll System 1.0. This affects the function upload of the file /marimar/guest/update.php. The manipulation of the argument image leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
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 Attendance and Payroll System 1.0 allows remote attackers to upload arbitrary files via the `image` parameter in the `upload` function of `/marimar/guest/update.php`. This can lead to remote code execution if malicious files (e.g., PHP webshells) are uploaded and accessed.
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 application installationLocate the SourceCodester Attendance and Payroll System installation directory on the web server. Look for typical web root locations (e.g., /var/www/html, C:\inetpub\wwwroot) containing the application files.Affected if The application files are present on the server in a publicly accessible web directory.
-
Verify the vulnerable file existsCheck if the file /marimar/guest/update.php exists in the web application directory. This is the specific endpoint containing the vulnerable upload function.Affected if The file /marimar/guest/update.php exists in the web application directory.
-
Identify the application versionExamine application metadata files (such as readme.txt, version.php, or similar documentation files) or check the database configuration for version indicators to confirm the installed version is 1.0.Affected if The installed version is confirmed to be exactly 1.0.
-
Determine if upload functionality is accessibleVerify that the /marimar/guest/update.php endpoint is reachable via HTTP/HTTPS from an unauthenticated or authenticated perspective. Attempt to access the page directly through a browser or curl request.Affected if The update.php page with the upload function is accessible and responds to requests.
-
Check upload directory writabilityExamine the application's upload directory configuration. Identify where uploaded files are stored (typically an 'uploads' or 'images' folder) and verify write permissions exist.Affected if The upload directory exists and is writable by the web server process.
If the SourceCodester Attendance and Payroll System version 1.0 is installed with the /marimar/guest/update.php file accessible, the application is likely vulnerable to unrestricted file upload leading to RCE.
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 validation (check MIME type and extension), rename uploaded files with random identifiers, store uploads outside the webroot, and disable script execution in the upload directory.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10420 — 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-2024-10420 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