CVE-2023-27440
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 vulnerability in OnTheGoSystems Types.This issue affects Types: from n/a through 3.4.17.
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 confidenceThe Types WordPress plugin by OnTheGoSystems has an unrestricted file upload vulnerability (CVSS 7.2) allowing attackers to upload files with dangerous types (e.g., executable PHP files). This could enable remote code execution if malicious files are uploaded to accessible web directories.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Verify Types plugin is installedCheck the WordPress plugins directory or admin panel for the 'Types' plugin by OnTheGoSystemsAffected if Types plugin is present in the installation
-
Identify installed Types plugin versionAccess the WordPress admin panel under Plugins > Installed Plugins and locate the Types plugin version number, or check the plugin header in wp-content/plugins/types/plugin.php for the 'Version' commentAffected if Version is present and is below 3.4.18
-
Confirm file upload functionality is in useCheck if the Types plugin's post relationship or file attachment fields are actively configured on any post types, or inspect the database for any postmeta entries related to Types upload fieldsAffected if Types file upload fields are configured and accepting file attachments
-
Inspect uploads directory for suspicious filesExamine wp-content/uploads/ and subdirectories for unexpected file extensions (.php, .phtml, .exe, .js) that were not intentionally uploaded through legitimate WordPress media functionalityAffected if Executable or suspicious file types exist in the uploads directory that were not explicitly intended
The environment is affected if the Types plugin version is below 3.4.18 and the plugin's upload functionality is enabled and accepting files.
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 · scopedUpgrade to Types version 3.4.18 or later which contains the fix for this unrestricted upload vulnerability. Until patched, monitor file uploads to the uploads directory and restrict script execution via .htaccess rules.
Types plugin version 3.4.18 or higher
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- 3. Locate the Types plugin in the list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the updated Types plugin from the official WordPress repository or OnTheGoSystems website
- 6. After updating, verify the plugin is running version 3.4.18 or higher under Plugins > Installed Plugins
- 7. Test that Types functionality (custom post types, taxonomies, fields) is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27440 — 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-27440 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