CVE-2018-10759
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 · uneditedPHP remote file inclusion vulnerability in public/patch/patch.php in Project Pier 0.8.8 and earlier allows remote attackers to execute arbitrary commands or SQL statements via the id parameter.
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 confidenceRemote file inclusion vulnerability in Project Pier's public/patch/patch.php allows attackers to execute arbitrary commands or SQL statements through the unprotected id parameter, which is used to include files without proper validation.
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<= 0.8.8CVSS 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.
-
Locate Project Pier installationSearch for Project Pier files on the server. Look for directories containing 'projectpier' or 'project_pier' folders, or check web server document roots for the application.Affected if Project Pier is installed on the server in any location
-
Identify installed versionCheck the version.php, version.txt, or similar version file in the Project Pier root directory. Common paths include version.php, application/config/version.php, or README files.Affected if The installed version is 0.8.8 or earlier, or if the version cannot be determined (assumed vulnerable)
-
Verify vulnerable file existsCheck if the file public/patch/patch.php exists in the Project Pier installation directory. This file should not be present in production deployments.Affected if The file public/patch/patch.php exists in the web-accessible directory
-
Check PHP allow_url_include settingReview php.ini or run 'php -i' or 'phpinfo()' to check if the PHP configuration directive allow_url_include is enabled.Affected if allow_url_include is set to On (1) in PHP configuration, which increases the severity of remote file inclusion
A user is affected if Project Pier version 0.8.8 or earlier is installed with the public/patch/patch.php file accessible on the web server, especially when PHP's allow_url_include is enabled.
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.
dbcve · scopedUpgrade from Project Pier 0.8.8 or earlier to a patched version; alternatively, disable PHP's allow_url_include setting and add strict input validation to the id parameter in patch.php.
- 1. Locate the file public/patch/patch.php in the ProjectPier installation directory
- 2. Rename the file to something non-executable (e.g., patch.php.disabled) or delete it entirely if not needed
- 3. If the patch functionality is required, restrict access to this file via web server configuration (e.g., .htaccess deny rule or web server access control)
- 4. Verify the vulnerability is no longer accessible by attempting to access the patch.php endpoint
- 5. Check for any other unauthenticated PHP files in public/ directories that may have similar vulnerabilities
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10759 — 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-10759 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