CVE-2021-36719
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 · uneditedPineApp - Mail Secure - The attacker must be logged in as a user to the Pineapp system. The attacker exploits the vulnerable nicUpload.php file to upload a malicious file,Thus taking over the server and running remote code.
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 confidenceAn authenticated file upload vulnerability in PineApp Mail Secure's nicUpload.php allows remote attackers with valid user credentials to upload malicious files, potentially achieving remote code execution and full server compromise.
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< 5.2.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed version of Mail SecureLocate the version information for Cybonet/PineApp Mail Secure in the system documentation, admin panel, or by querying the installed package - compare the version number against the affected range (all versions below 5.2.1)Affected if The installed version is lower than 5.2.1
-
Locate the nicUpload.php fileSearch the web root directory for the file named nicUpload.php - typical locations include /var/www/html, /web, or the document root configured for the web serverAffected if The file nicUpload.php exists on the server
-
Verify file accessibilityAttempt to access nicUpload.php via HTTP/HTTPS using the server's configured web URL (e.g., curl http://yourserver.com/nicUpload.php)Affected if The file is reachable over the network and responds to HTTP requests
-
Confirm authentication is activeCheck whether the Mail Secure web interface authentication is functioning - verify that user login credentials are accepted by the systemAffected if Valid user credentials can be used to authenticate to the Mail Secure web interface
The environment is affected if the installed Cybonet Mail Secure version is below 5.2.1 AND the nicUpload.php file exists and is accessible, especially when web interface authentication is enabled.
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.
dbcve · scoped5.2.1
Disable or restrict access to the vulnerable nicUpload.php file, implement strict server-side file type validation and content inspection, store uploaded files outside the web root, and apply vendor security patches immediately.
5.2.1 or later
- Obtain the PineApp Mail Secure version 5.2.1 or later from the official vendor
- Backup the current Mail Secure configuration and all mail data
- Follow the vendor's official upgrade documentation for Mail Secure
- Verify the nicUpload.php file has been updated or removed as part of the patch
- Confirm the upgrade was successful and test that file upload functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36719 — 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-2021-36719 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