CVE-2023-27397
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 · uneditedUnrestricted upload of file with dangerous type exists in MicroEngine Mailform version 1.1.0 to 1.1.8. If the product's file upload function and server save option are enabled, a remote attacker may save an arbitrary file on the server and execute it.
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 confidenceMicroEngine Mailform versions 1.1.0 to 1.1.8 contains an unrestricted file upload vulnerability. When the file upload function and server save option are enabled, remote attackers can upload arbitrary files (including executable files) to the server and subsequently execute them, achieving remote code execution.
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.1.0, < 1.1.9CVSS 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.
-
Check installed MicroEngine Mailform versionLocate the version information for your MicroEngine Mailform installation (typically in the product documentation, about page, or version file)Affected if Version is greater than or equal to 1.1.0 and less than 1.1.9
-
Verify file upload function statusInspect the MicroEngine Mailform configuration settings to determine if the file upload feature is enabledAffected if File upload function is currently enabled
-
Verify server save option statusInspect the MicroEngine Mailform configuration settings to determine if the server save option is enabledAffected if Server save option is currently enabled
-
Check upload directory placementExamine the upload directory configuration to determine if uploaded files are stored within the webrootAffected if Upload directory is located inside the webroot and accessible via HTTP
-
Check file type validation configurationReview the file upload validation settings to see if a strict allowlist is implementedAffected if No strict allowlist-based file type validation is configured or validation relies only on file extensions
Your environment is affected if MicroEngine Mailform version is between 1.1.0 and 1.1.8 AND both the file upload function and server save option are 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 · scoped1.1.9
Immediately disable the file upload function or server save option if not required. If needed, implement strict allowlist-based file type validation, validate file contents (not just extensions), store uploads outside webroot, and ensure uploaded files are not executable.
1.1.9
- Upgrade MicroEngine Mailform to version 1.1.9 or later to resolve the unrestricted file upload vulnerability
- After upgrading, verify that the file upload function and server save option are properly configured according to security best practices
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-27397 — 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-2023-27397 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