dbcve.org
SuphpApplication

CVE-2014-1867

HIGH · 7.8 CVSS v3.1 Published 2019-12-13
Fix available
A fix is available. Upgrade to 0.7.2 or later.
See remediation →
80/100
Remediation priority · High
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
suPHP before 0.7.2 source-highlighting feature allows security bypass which could lead to arbitrary code execution

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 confidence

The suPHP component's source-highlighting feature in versions prior to 0.7.2 contains a security bypass that allows an attacker to execute arbitrary code, likely through improper validation or path handling within the syntax highlighting functionality.

MitigationUpgrade suPHP to version 0.7.2 or later to patch the source-highlighting security bypass. If immediate upgrading is not feasible, disable the source-highlighting feature if possible and ensure the server is not exposed to untrusted PHP code.

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
SuphpApplication
Affected:< 0.7.2

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check if suPHP is installed
    Run command 'suphp -v' or 'suphp -h' to see if the suPHP binary is present and functional on the system. On Linux systems, you may also check for suPHP via package manager: 'dpkg -l | grep suphp' or 'rpm -qa | grep suphp'.
    Affected if suPHP is not installed on the system, so the vulnerability does not apply.
  2. Determine installed suPHP version
    Execute 'suphp -v' to display version information. Compare the displayed version number against the affected range: versions prior to 0.7.2 are vulnerable.
    Affected if The installed version is below 0.7.2, placing it within the vulnerable range.
  3. Locate suPHP configuration file
    Common locations include /etc/suphp.conf, /etc/suphp/suphp.conf, or within Apache configuration directories (e.g., /etc/apache2/mods-available/suphp.conf). Search for files containing 'suphp' and 'source-highlight'.
    Affected if Unable to locate suPHP configuration file.
  4. Check if source-highlighting feature is enabled
    Open the suPHP configuration file and search for directives related to source-highlighting, such as 'source-highlight', 'highlight', or 'syntax-highlight'. Verify whether these features are set to 'true', 'enabled', or a non-empty value.
    Affected if source-highlighting is enabled in the configuration, exposing the vulnerable code path.
  5. Verify Apache/web server uses suPHP handler
    Check Apache configuration (httpd.conf, apache2.conf, or vhost files) for lines containing 'suPHP_Handler' or 'AddHandler su-php' to confirm suPHP is actively handling PHP requests.
    Affected if suPHP is not configured as the PHP handler, reducing exposure but not eliminating the vulnerability if suPHP is installed.

The environment is affected if suPHP version 0.7.2 or higher is not installed AND the source-highlighting feature is enabled in the configuration.

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.

From vendor data
Upgrade available Upgrade to 0.7.2 or later
Fixed in 0.7.2
Interim mitigation

Upgrade suPHP to version 0.7.2 or later to patch the source-highlighting security bypass. If immediate upgrading is not feasible, disable the source-highlighting feature if possible and ensure the server is not exposed to untrusted PHP code.

Fix this in Suphp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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