CVE-2026-22327
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 · uneditedSubscriber Arbitrary File Upload in Restaurt <= 1.0.4 versions.
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 confidenceArbitrary file upload vulnerability in Restaurt CMS versions 1.0.4 and below allows authenticated users with subscriber privileges to upload arbitrary files, likely due to insufficient validation of file types and content, potentially enabling remote code execution.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Restaurant CMS installationSearch for Restaurant CMS web application files, typically found in web root directories (check for directories named 'restaurant', 'restaurant-cms', or similar CMS-specific folder structures containing restaurant-related content)Affected if Restaurant CMS software is present in the environment
-
Determine installed CMS versionLocate the version file or version information typically found in CMS administration panels, README files, or configuration files within the Restaurant CMS installation directoryAffected if Installed version is 1.0.4 or lower (any version at or below 1.0.4)
-
Verify file upload feature is enabledCheck CMS configuration settings or plugin/module status for file upload functionality - look for file upload endpoints or media upload features in the web applicationAffected if File upload module or feature is active and accessible to users
-
Confirm subscriber-level user accounts existReview user role definitions in the CMS database or user management interface to identify accounts assigned subscriber or similar low-privilege rolesAffected if Any subscriber-privileged or low-privilege user accounts exist in the system
-
Inspect upload directory configurationExamine the CMS upload path configuration and server configuration for the upload directory - check if script execution is disabled in upload pathsAffected if Upload directories allow script execution or lack proper access restrictions
Environment is affected if Restaurant CMS version 1.0.4 or below is installed with the file upload feature enabled and at least one subscriber-privileged user account exists, particularly if upload directories permit script execution.
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 · scopedUpdate to a version newer than 1.0.4; if no patch available, implement strict server-side file type validation, restrict upload directories, and disable script execution in upload paths.
Restaurt version > 1.0.4 (latest available version)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Restaurt' plugin/theme
- Check the current version - if it is 1.0.4 or below, an update is needed
- Update the plugin to the latest available version from the WordPress repository or vendor
- Verify the update was successful by checking the installed version number
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-2026-22327 — 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-2026-22327 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