ElmouradiAmine/CVE-2020-7048

GitHubRepository PoC

PoC files

4 files

File viewing is interactive and short-lived. Downloads are password-protected ZIP archives using password eip.

GitHub

Docker lab environments

1
GitHub

docker-compose.yml

Created Vuln labCVE-2020-7048Compose · images

1 Compose manifest · 3 services

Analysisdeepseek-v4-pro:cloud ·

Environment assessment

A Docker Compose environment defining three services: a MySQL 5.7 database, a phpMyAdmin interface, and a WordPress instance. The WordPress service bind-mounts the current host directory into /var/www/html, making local files (including a WordPress plugin zip and a README referencing CVE-2020-7048) available inside the container.

docker-compose.yml:1-48

Lab assessment

Vulnerability lab

The repository is named after CVE-2020-7048, the README explicitly references that CVE and links to a reproduction video, and the Compose file includes a WordPress service with a bind mount that exposes a plugin zip (wordpress-database-reset.3.1.zip) likely related to the vulnerability. This structure is consistent with a vulnerability reproduction environment.

README.md:1-3docker-compose.yml:30-31
Lab shapeCompose · images
Services3
Compose manifests1
Dockerfiles0
Evidence & reasoningComponents · CVE assessment · exercise context · review boundaries
Components

Services and files described by the evidence

db

database server

MySQL 5.7 database service with a persistent volume for data storage. It is configured with a root password, a wordpress database, and a wordpress user.

docker-compose.yml:5-14

phpmyadmin

database administration interface

phpMyAdmin service that depends on the db service and exposes port 3306 on the host mapped to container port 80. It connects to the db service using the root password.

docker-compose.yml:16-26

wordpress

web applicationvulnerable target

WordPress latest image that depends on the db service and exposes port 8000 on the host mapped to container port 80. It bind-mounts the current host directory (.) into /var/www/html, which includes a WordPress plugin zip (wordpress-database-reset.3.1.zip) and a README referencing CVE-2020-7048. This mount likely provides the vulnerable plugin for exploitation.

docker-compose.yml:28-40README.md:1-3
CVE assessment

How the supplied evidence relates each vulnerability

CVE-2020-7048

Insufficient evidence

The README mentions CVE-2020-7048 and links to a reproduction video, and the environment includes a WordPress plugin zip (wordpress-database-reset.3.1.zip) that may be the vulnerable component. However, no exploit code, configuration details, or vulnerability description is provided in the packet to confirm the CVE association or demonstrate the vulnerability.

README.md:1-3
Exercise context

Requirements and sequence described by the evidence

Prerequisites

  • Docker and Docker Compose must be installed to run the environment.docker-compose.yml:1
  • The WordPress plugin wordpress-database-reset.3.1.zip must be present in the bind-mounted directory and likely needs to be installed and activated in the WordPress instance.docker-compose.yml:30-31

Evidence-described exercise path

  1. Start the Docker Compose environment to bring up the database, phpMyAdmin, and WordPress services.docker-compose.yml:1-48
  2. Access the WordPress instance on host port 8000 and complete the installation, including setting up the site and activating the wordpress-database-reset plugin from the mounted zip file.docker-compose.yml:30-31
  3. Follow the reproduction steps from the linked video to exploit CVE-2020-7048 in the WordPress database reset plugin.README.md:2
Safety-review evidence

Behaviors behind the stored safety assessment

No harmful behavior observed

The Compose file defines a standard WordPress development stack with a bind mount to provide a plugin. No hidden or unnecessary host escape, persistence, credential theft, or external communication is visible. The bind mount is a common lab practice to inject vulnerable components. The environment targets only the lab's own services.

docker-compose.yml:1-48
Review boundaries

What the analysis did not establish

  • The packet contains two binary files (.DS_Store and wordpress-database-reset.3.1.zip) that are uninspected; their contents could alter the safety assessment.
  • No exploit code or detailed vulnerability description is provided, so the exact exploitation path and CVE association cannot be verified.
  • The README references an external video, but its content is not included in the packet.
Model interpretation

This review is limited to the supplied lab evidence packet. It does not assert that the environment runs, reproduces a vulnerability, or is safe to execute. Contract: eip-docker-lab-analysis-v1.

Packet coverage: 2 binary files not inspected

Linked vulnerabilities

1