CVE-2020-37080
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 · uneditedwebTareas 2.0.p8 contains a file deletion vulnerability in the print_layout.php administration component that allows authenticated attackers to delete arbitrary files. Attackers can exploit the vulnerability by manipulating the 'atttmp1' parameter to specify and delete files on the server through an unauthenticated file deletion mechanism.
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 confidencewebTareas 2.0.p8 contains a file deletion vulnerability in the print_layout.php administration component. Authenticated attackers can manipulate the 'atttmp1' parameter to specify and delete arbitrary files on the server, likely due to insufficient input validation and authorization checks on the file path.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 webTareas installation and versionLocate webTareas on the server and determine the installed version by examining version files, headers, or application metadataAffected if The installed version matches or precedes 2.0.p8 (the affected version range)
-
Locate print_layout.php fileSearch the webTareas installation directory for the print_layout.php file, typically found in admin or administration pathsAffected if The print_layout.php file exists in the webTareas installation
-
Verify atttmp1 parameter handlingExamine the print_layout.php source code to see how the 'atttmp1' parameter is processed and whether file path inputs are validated before deletion operationsAffected if The 'atttmp1' parameter accepts file paths without proper sanitization or path traversal protection
-
Check authentication requirements for print_layout.phpReview how print_layout.php handles authentication and authorization - test whether unauthenticated or low-privilege users can access the file deletion functionalityAffected if The component lacks proper authentication checks or allows authenticated users to delete files outside expected directories
A user is affected if webTareas 2.0.p8 (or earlier versions) is installed, the print_layout.php file exists, and the 'atttmp1' parameter can be manipulated to delete arbitrary files without proper validation or authorization controls.
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 dataRestrict file deletion to authorized users only and implement strict input validation on the 'atttmp1' parameter to prevent directory traversal and ensure only intended files can be deleted. Consider removing direct file operations from the web application entirely or using whitelisted file paths.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-37080 — 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-2020-37080 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