dbcve.org
OnefilecmsApplication

CVE-2018-13123

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-03
Fix available
A fix is available. Upgrade to after 2017-10-09 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
onefilecms.php in OneFileCMS through 2017-10-08 might allow attackers to read arbitrary files via the i and f parameters, as demonstrated by ?i=etc/&f=passwd&p=raw_view for the /etc/passwd file.

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 confidence

OneFileCMS through 2017-10-08 contains a path traversal vulnerability in onefilecms.php. Attackers can read arbitrary files on the server by manipulating the i (directory) and f (filename) parameters, as demonstrated by reading /etc/passwd via ?i=etc/&f=passwd&p=raw_view.

MitigationImplement strict input validation and sanitization on the i and f parameters to prevent directory traversal sequences. Disable or restrict the raw_view functionality if not required, or upgrade to a patched version if available.

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
OnefilecmsApplication
Affected:<= 2017-10-09

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate OneFileCMS installation
    Search the web server document root for the file onefilecms.php. Common paths include /var/www/html/, /var/www/, or the web root directory. Use: find /var/www -name 'onefilecms.php' 2>/dev/null
    Affected if The file onefilecms.php exists on the server and is web-accessible.
  2. Determine OneFileCMS version
    Open onefilecms.php in a text editor or via command line and look for a version string or date marker near the top of the file, typically in comments or a defined version constant. Compare this date to 2017-10-09.
    Affected if The file shows a version or date <= 2017-10-09.
  3. Verify raw_view parameter is processed
    Examine the PHP code around line handling the 'p' parameter. Search for a code block that processes the raw_view value, for example: if(isset($_GET['p']) && $_GET['p'] === 'raw_view'). Check if this functionality is not commented out or disabled.
    Affected if The raw_view parameter handling code exists and is active in the file.
  4. Confirm vulnerable parameter handling exists
    Search the onefilecms.php source for how the 'i' (directory) and 'f' (filename) GET parameters are used. Look for code that directly passes these parameters to file operations without sanitization, such as file_get_contents or fopen using the parameter values.
    Affected if Code directly uses $_GET['i'] and $_GET['f'] in file operations without validation.

A server is affected if it runs OneFileCMS version 2017-10-09 or earlier with onefilecms.php accessible via the web and the raw_view parameter functional.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2017-10-09
Interim mitigation

Implement strict input validation and sanitization on the i and f parameters to prevent directory traversal sequences. Disable or restrict the raw_view functionality if not required, or upgrade to a patched version if available.

Recommended fix Moderate confidence

Any version of OneFileCMS released after 2017-10-09 (verify the specific fixed release on GitHub)

  1. 1. Navigate to the OneFileCMS GitHub repository (github.com/squibix/OneFileCMS or similar OneFileCMS repository)
  2. 2. Locate the releases or commits after October 2017 (specifically after 2017-10-09)
  3. 3. Identify the version that includes the security fix for the path traversal vulnerability (CVE-2018-13123)
  4. 4. Download or clone the fixed version of onefilecms.php
  5. 5. Replace the vulnerable onefilecms.php file with the fixed version
  6. 6. Verify the fix by attempting to access /etc/passwd via the vulnerable parameter pattern (?i=etc/&f=passwd&p=raw_view) - it should now be blocked
  7. 7. Test that legitimate file operations still work correctly
Caveat Review changelog for any configuration or behavior changes between versions; minor PHP compatibility considerations may apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Onefilecms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13123 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13123 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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