dbcve.org
PhpcmsApplication · Phpcms Project

CVE-2018-14399

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
libs\classes\attachment.class.php in PHPCMS 9.6.0 allows remote attackers to upload and execute arbitrary PHP code via a .txt?.php#.jpg URI in the SRC attribute of an IMG element within info[content] JSON data to the index.php?m=member&c=index&a=register 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 confidence

The attachment.class.php in PHPCMS 9.6.0 has a file upload validation bypass where attackers exploit the registration endpoint (index.php?m=member&c=index&a=register) to upload malicious PHP files. By using a crafted filename (.txt?.php#.jpg) in an IMG element's SRC attribute within info[content] JSON data, the validation logic can be circumvented, allowing arbitrary PHP code execution on the server.

MitigationRestrict or disable member registration if not required, implement strict server-side file type validation excluding .php extensions, and deploy a WAF as an interim control until the vendor patch is applied.

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
PhpcmsApplication
Affected:= 9.6.0

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. Verify PHPCMS version
    Locate the version file or admin panel to determine the installed PHPCMS version. Common locations include a version.php file in the core directory or the administrator dashboard.
    Affected if The installed version is exactly 9.6.0. If the version differs (higher or lower), this specific CVE does not apply.
  2. Confirm member registration is enabled
    Check if the user registration feature is active on the site by navigating to the registration endpoint (index.php?m=member&c=index&a=register) or by examining the site configuration settings.
    Affected if Member registration is publicly accessible and enabled. If registration is disabled at the server level or in the CMS configuration, the attack surface does not exist.
  3. Inspect uploaded files directory for unexpected PHP files
    Examine the upload directories (typically /uploadfile/ or similar paths configured in attachment.class.php) for any .php files that were not intentionally placed there by administrators.
    Affected if Arbitrary PHP files exist in upload directories, indicating successful exploitation of the validation bypass.

You are affected if your PHPCMS installation is exactly version 9.6.0 AND member registration is enabled, allowing attackers to bypass file upload validation through crafted filenames.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable member registration if not required, implement strict server-side file type validation excluding .php extensions, and deploy a WAF as an interim control until the vendor patch is applied.

Recommended fix Moderate confidence

PHPCMS 9.6.3 or latest stable release

  1. 1. Backup the entire PHPCMS installation directory and database before making any changes.
  2. 2. Navigate to the official PHPCMS download repository or your system's package manager.
  3. 3. Download the latest stable release of PHPCMS (version 9.6.3 or later if available).
  4. 4. Replace the existing 'libs/classes/attachment.class.php' file with the updated version from the new release.
  5. 5. Clear any cached files in the '/cache/' directory to ensure the new code is loaded.
  6. 6. Test the registration functionality to confirm the fix works correctly.
  7. 7. Monitor server logs for any suspicious activity or repeated attack attempts.
Caveat Review custom modifications to attachment.class.php before upgrading as they may need to be reapplied

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

Fix this in Phpcms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14399 — 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-14399 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