CVE-2018-13122
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 · uneditedonefilecms.php in OneFileCMS through 2017-10-08 might allow attackers to delete arbitrary files via the Delete File(s) screen, as demonstrated by a ?i=var/www/html/&f=123.php&p=edit&p=deletefile URI.
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 confidenceOneFileCMS through 2017-10-08 contains a path traversal vulnerability in the Delete File(s) function of onefilecms.php. Attackers can delete arbitrary files on the server by manipulating the 'i' (path) and 'f' (filename) URL parameters to reference files outside the intended directory, as demonstrated by the URI pattern ?i=var/www/html/&f=123.php&p=edit&p=deletefile.
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<= 3.6.13CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Locate OneFileCMS installationSearch the web server document root for onefilecms.php file, typically in /var/www/html/ or similar web directoriesAffected if onefilecms.php exists on the server
-
Identify installed versionOpen onefilecms.php in a text editor and search for a version string near the top of the file, often in a variable like $version or in commentsAffected if version number found is 3.6.13 or lower
-
Verify delete function is accessibleCheck if the web server serves OneFileCMS and if the delete functionality is enabled by accessing the login page or checking for the 'deletefile' parameter support in the source codeAffected if the OneFileCMS web interface is accessible and the deletefile function exists in the code
-
Confirm path traversal vulnerability existsReview the onefilecms.php code around the delete file function, specifically looking at how the 'i' and 'f' parameters are processed before file deletion operationsAffected if the code uses the 'i' and 'f' parameters without validating that the resulting path stays within the webroot directory
If OneFileCMS version 3.6.13 or lower is installed and the web interface is accessible, the server is vulnerable to path traversal via the 'i' and 'f' parameters in the delete file function.
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 dataImplement strict input validation to ensure the file path resolves to a location within the allowed webroot directory. Use realpath() to canonicalize paths and verify the resulting path starts with the expected base directory before allowing deletion.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13122 — 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-2018-13122 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