Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2017-15715-httpd — Proof-of-concept exploit for CVE-2017-15715, demonstrating Apache HTTPD mod_php file upload bypass using a trailing newline character to execute arbitrary PHP files. | Kitploit
Tools/GitHubGitHub/ehsehs5652/cve-2017-15715-httpd
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityPenetration TestingLearning & Education
GitHubehsehs5652/cve-2017-15715-httpd

CVE-2017-15715-httpd

Proof-of-concept exploit for CVE-2017-15715, demonstrating Apache HTTPD mod_php file upload bypass using a trailing newline character to execute arbitrary PHP files.

View Repository
264 months agoNot yet reviewed
Share

CVE-2017-15715-httpd

WHS 4th Container Assignment

Summary

Apache HTTPD is a widely used HTTP server that can run PHP web pages through mod_php. From versions 2.4.0 to 2.4.29, there is a parsing vulnerability where a file name ending in .php, such as 1.php\x0A, is recognized as a PHP file, allowing an attacker to bypass certain server security policies.

References

https://httpd.apache.org/security/vulnerabilities_24.html https://security.elarlang.eu/cve-2017-15715-apache-http-server-filesmatch-bypass-with-a-trailing-newline-at-the-end-of-the-file-name.html

Environment Setup

Run the following commands to set up a vulnerable Apache HTTPD server ''' docker compose build docker compose up -d '''

Once the server starts, Apache runs at http://my-ip:8080, generated based on my IP address.

Vulnerability Reproduction

First, when you submit a file named 1.php, the security check blocks it and the request is rejected with a 'bad file' message.

1.php upload failure screen

However, by adding a newline character and submitting 1.php again, you can see it is successfully uploaded. (This was done by adding 0a next to the name in the Hex values in Burp Suite.)

Burp Suite Hex edit screen

When accessing '/1.php%0a', it is successfully parsed as a PHP file despite the lack of a proper PHP extension. This confirms the existence of a parsing vulnerability.

PHP file execution result

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    851
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    538
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    420
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    297
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →