Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2023-27372 — Safe PoC scanner and Docker lab for CVE-2023-27372, an RCE in SPIP CMS before 4.2.1. Verifies vulnerability via password recovery endpoint without destructive actions. | Kitploit
Tools/GitHubGitHub/kiroloskhairy/cve-2023-27372
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingLearning & EducationLabs & Practice
GitHubkiroloskhairy/cve-2023-27372

CVE-2023-27372

Safe PoC scanner and Docker lab for CVE-2023-27372, an RCE in SPIP CMS before 4.2.1. Verifies vulnerability via password recovery endpoint without destructive actions.

View Repository
37 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Research Project: CVE-2023-27372 — SPIP (RCE, Lab Environment + Safe PoC)


1) Description

This repository contains:

  • stand/ — a lab environment (vulnerable setup) on Docker: SPIP + MariaDB.
  • poc/ — a Python verification tool (scanner) implementing safe confirmation of the vulnerability (Safe PoC) without destructive actions.

The project is intended for demonstration and analysis of the vulnerability CVE-2023-27372 in SPIP prior to 4.2.1. The check is performed through the password recovery functionality (endpoint spip.php?page=spip_pass) and confirmed by executing a safe command on the lab side.


2) Repository Structure

root@kitploit:~
.
├── stand/                 # Vulnerable lab (SPIP + MariaDB) on Docker Compose
│   ├── docker-compose.yml
│   └── ... (Dockerfile/lab scripts, persist volumes, etc.)
└── poc/                   # Safe PoC scanner (Python)
    ├── Dockerfile
    ├── README.md          # (optional) local PoC documentation
    └── src/
        ├── scanner.py
        ├── utils.py
        └── pyproject.toml

3) Quick Start (Local Lab)

3.1 Launch Vulnerable Lab

root@kitploit:~
cd stand
docker compose up -d
docker compose ps

The service will be available at:

  • http://127.0.0.1:8080/
  • Login page: http://127.0.0.1:8080/spip.php?page=login

4) Running Safe PoC (scanner)

4.1 Build the Image

Navigate to poc/ and build the scanner Docker image:

root@kitploit:~
cd ../poc

# If your environment experiences DNS issues during the build, use:
docker build --network=host -t spip-poc-scanner .

If there are no DNS problems, you can use the normal command:

root@kitploit:~
docker build -t spip-poc-scanner .

4.2 Run the Check

Recommended command for the local lab:

root@kitploit:~
docker run --rm --network="host" \
  -v "$(pwd)":/app/out \
  spip-poc-scanner \
  -i http://127.0.0.1:8080 \
  -o /app/out/results.json

5) Results and PoC Confirmation

5.1 Results File

After execution, results.json will be created (example structure):

root@kitploit:~
[
  {
    "ip": "http://127.0.0.1:8080",
    "vuln": true
  }
]

5.2 Execution Confirmation (Safe Check)

If your PoC implementation confirms execution by creating a file (e.g., /tmp/pwned.txt), you can verify this inside the web container.

Option without a hardcoded container name:

root@kitploit:~
cd ../stand
WEB_CID="$(docker compose ps -q web)"
docker exec "$WEB_CID" ls -l /tmp/pwned.txt

If the file exists, this confirms the possibility of command execution within the lab environment.


6) Requirements

  • Docker
  • Docker Compose (v2)
  • (optional) Internet access during the initial PoC image build (if dependencies are installed via pip)

7) Technical Reference

  • CVE: CVE-2023-27372
  • Product: SPIP CMS
  • Vulnerable versions: prior to 4.2.1
  • Class: improper data handling during password recovery (leads to code execution in vulnerable versions)
  • Entry point: spip.php?page=spip_pass

8) Troubleshooting

8.1 Temporary failure in name resolution during docker build

Use the host network build:

root@kitploit:~
docker build --network=host -t spip-poc-scanner .

8.2 Need to "reset" the lab to a clean state

Stop and remove volumes:

root@kitploit:~
cd stand
docker compose down -v
docker compose up -d

9) Disclaimer.

This project was created solely for educational use and legal testing in your own lab environment. The author is not responsible for any unauthorized use.

---::contentReference[oaicite:0]{index=0}

Download Tool