CVE-2023-54335
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 · uneditedeXtplorer 2.1.14 contains an authentication bypass vulnerability that allows attackers to login without a password by manipulating the login request. Attackers can exploit this flaw to upload malicious PHP files and execute remote commands on the vulnerable file management system.
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 confidenceeXtplorer 2.1.14 has an authentication bypass vulnerability where attackers can login without a password by manipulating the login request. Once authenticated, they can upload malicious PHP files and execute remote commands 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<= 2.1.14CVSS 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 if eXtplorer is installedSearch for eXtplorer files in your web root directories. Common locations include /extplorer/, /administrator/components/com_extplorer/, or look for 'eXtplorer' or 'extplorer' directories in your web application folder structure.Affected if eXtplorer is present on the server in any directory.
-
Check the installed eXtplorer versionLocate the version file or header within the eXtplorer installation. Common places include a version.php file, a config file, or the main index.php which often displays the version. Compare the found version to the affected range: <= 2.1.14.Affected if The installed version is 2.1.14 or lower.
-
Verify network exposure of eXtplorerDetermine if the eXtplorer application is accessible from the network by attempting to access its login page via HTTP/HTTPS from an external host, or by reviewing firewall and web server configurations that expose the application.Affected if The eXtplorer login page is accessible from untrusted networks.
-
Inspect for suspicious PHP files in upload directoriesSearch for newly created PHP files in eXtplorer upload directories, typically under the 'files' or 'home' folders within the eXtplorer installation. Review file creation dates around the time of potential compromise.Affected if Unexpected PHP files exist in eXtplorer upload directories, especially files not created by legitimate administrators.
-
Review eXtplorer user accounts for unauthorized accessCheck the eXtplorer user configuration database or user files for added or modified administrator accounts that were not created by legitimate administrators.Affected if Unexpected user accounts exist in eXtplorer, or known administrator accounts show suspicious login activity.
A server is affected if eXtplorer version 2.1.14 or lower is installed and accessible over the network, allowing remote attackers to bypass authentication and upload 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.
From vendor dataUpgrade eXtplorer to the latest patched version. If immediate patching is not possible, disable the application, restrict network access, or implement additional authentication controls such as web application firewall rules or IP-based restrictions.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-54335 — 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-54335 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