CVE-2022-50912
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 · uneditedImpressCMS 1.4.4 contains a file upload vulnerability with weak extension sanitization that allows attackers to upload potentially malicious files. Attackers can bypass file upload restrictions by using alternative file extensions .php2.php6.php7.phps.pht to execute arbitrary PHP code on 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 confidenceImpressCMS 1.4.4 has a file upload vulnerability where extension sanitization only blocks common PHP extensions but fails to block alternative PHP extensions (.php2, .php6, .php7, .phps, .pht). Attackers can upload files with these bypass extensions to execute arbitrary PHP code on the server.
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.4.4CVSS 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 the installed ImpressCMS versionLocate the version file or check the admin dashboard for the ImpressCMS version numberAffected if The installed version is 1.4.4
-
Verify if file upload functionality existsAccess the ImpressCMS admin panel and check for modules that allow file uploads (such as profile uploads, content attachments, or media management)Affected if File upload features are enabled and accessible to users
-
Test extension validation for .php2, .php6, .php7, .phps, .phtAttempt to upload a file with one of the alternative PHP extensions (.php2, .php6, .php7, .phps, .pht) through the file upload functionalityAffected if The upload is successful and the file is stored on the server with the bypassed extension
-
Confirm uploaded files are web-accessibleCheck if files with bypassed PHP extensions can be accessed via a web browser (navigate to the uploaded file URL)Affected if The uploaded file with an alternative PHP extension is directly accessible and could execute code
A user is affected if they are running ImpressCMS 1.4.4 with any file upload functionality that accepts these alternative PHP extensions and serves them via the web.
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 · scopedImplement comprehensive extension validation that blocks all PHP-related extensions and switch to content-based file type validation using magic bytes rather than relying solely on file extensions.
Latest stable ImpressCMS release (version > 1.4.4)
- 1. Backup the current ImpressCMS installation and database before making any changes.
- 2. Download the latest stable version of ImpressCMS from the official repository at github.com/ImpressCMS.
- 3. Replace the core files with the new version, preserving custom configurations and modules.
- 4. Verify file upload functionality works correctly with legitimate file types.
- 5. Monitor server logs for any suspicious file upload attempts using extensions like .php2, .php3, .php4, .php5, .php6, .php7, .phps, or .pht.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-50912 — 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-50912 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