CVE-2023-27083
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 · uneditedAn issue discovered in /admin.php in Pluck CMS 4.7.15 through 4.7.16-dev5 allows remote attackers to run arbitrary code via manage file functionality.
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 confidencePluck CMS 4.7.15 through 4.7.16-dev5 contains a remote code execution vulnerability in the manage file functionality of admin.php, allowing remote attackers to execute arbitrary 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>= 4.7.15, < 4.7.16= 4.7.16CVSS 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.
-
Identify Pluck CMS versionCheck the version.php file or admin dashboard for the installed Pluck CMS version numberAffected if The installed version is 4.7.15, 4.7.16, or any version between 4.7.15 and 4.7.16 (including development builds up to 4.7.16-dev5)
-
Locate admin.phpLocate the admin.php file in the Pluck CMS installation directory on the web serverAffected if The admin.php file exists in the web-accessible directory
-
Verify file management module is activeCheck if the file management functionality is enabled in the admin panel under the manage files sectionAffected if The manage files or file management module is accessible and enabled for the CMS
-
Confirm web server access to admin.phpTest whether the admin.php file is accessible via HTTP/HTTPS from the web serverAffected if admin.php is accessible without authentication or with compromised admin credentials
A system is affected if it runs Pluck CMS versions 4.7.15 through 4.7.16 (including dev5) and has the admin.php file management functionality accessible to the attacker.
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 · scoped4.7.16
Upgrade to a patched version of Pluck CMS if available, or disable/restrict access to the file management functionality in admin.php until a fix is available.
Pluck CMS 4.7.16 or latest stable release
- 1. Verify your current Pluck CMS version by logging into the admin panel or checking the version file
- 2. Download the latest stable version of Pluck CMS (4.7.16 or later) from the official source
- 3. Back up your entire Pluck CMS installation including database and all files
- 4. Replace the existing Pluck CMS files with the new version files
- 5. Verify the file upload functionality in /admin.php now properly validates and restricts file types
- 6. Test that the manage file functionality works correctly with allowed file types
- 7. Confirm the installation is working properly and monitor for any issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27083 — 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-27083 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