CVE-2022-22793
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 · uneditedCybonet - PineApp Mail Relay Local File Inclusion. Attacker can send a request to : /manage/mailpolicymtm/log/eml_viewer/email.content.body.php?filesystem_path=ENCDODED PATH and by doing that, the attacker can read Local Files inside the server.
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 confidenceLocal File Inclusion (LFI) vulnerability in Cybonet PineApp Mail Relay allows remote attackers to read arbitrary local files on the server by manipulating the filesystem_path parameter in the /manage/mailpolicymtm/log/eml_viewer/email.content.body.php endpoint. The attacker provides an encoded file path, bypassing basic validation and accessing sensitive system files.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Cybonet PineApp Mail Secure installationIdentify if the system has PineApp Mail Secure installed. Check for typical installation directories or look for PineApp-related processes and services running on the mail server.Affected if The system is running Cybonet PineApp Mail Secure (any version)
-
Verify the vulnerable PHP endpoint existsCheck for the existence of the file email.content.body.php in the /manage/mailpolicymtm/log/eml_viewer/ directory. On the filesystem, locate this path within the web root of the PineApp installation.Affected if The file /manage/mailpolicymtm/log/eml_viewer/email.content.body.php exists on the server
-
Test filesystem_path parameter acceptanceSend an HTTP request to the endpoint /manage/mailpolicymtm/log/eml_viewer/email.content.body.php with a crafted filesystem_path parameter (e.g., using path traversal such as ../../../../etc/passwd encoded or raw). Observe if the application returns file contents or processes the path.Affected if The endpoint accepts and processes the filesystem_path parameter, returning file contents outside the intended directory
A user is affected if the system runs Cybonet PineApp Mail Secure and the vulnerable endpoint at /manage/mailpolicymtm/log/eml_viewer/email.content.body.php accepts and returns arbitrary file contents via the filesystem_path parameter.
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 input validation and whitelist-based filtering on the filesystem_path parameter to prevent path traversal sequences; restrict access to the vulnerable endpoint and apply principle of least privilege.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22793 — 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-22793 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