Vulnerabilities > CVE-2023-52146 - Information Exposure Through Log Files vulnerability in Ajexperience 404 Solution

CVSS 5.3 - MEDIUM

Attack vector

NETWORK

Attack complexity

LOW

Privileges required

NONE

Confidentiality impact

LOW

Integrity impact

NONE

Availability impact

NONE

network

low complexity

ajexperience

CWE-532

NVD

Published: 2024-01-05

Updated: 2024-02-06

Summary

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Aaron J 404 Solution.This issue affects 404 Solution: from n/a through 2.33.0.

Vulnerable Configurations

Part	Description	Count
Application	Ajexperience Ajexperience 404 Solution 1.5.0 Ajexperience 404 Solution 1.5.1 Ajexperience 404 Solution 1.5.2 Ajexperience 404 Solution 1.5.3 Ajexperience 404 Solution 1.5.4 Ajexperience 404 Solution 1.5.5 Ajexperience 404 Solution 1.5.6 Ajexperience 404 Solution 1.5.7 Ajexperience 404 Solution 1.5.8 Ajexperience 404 Solution 1.5.9 Ajexperience 404 Solution 1.6.0 Ajexperience 404 Solution 1.6.1 Ajexperience 404 Solution 1.6.2 Ajexperience 404 Solution 1.6.3 Ajexperience 404 Solution 1.6.4 Ajexperience 404 Solution 1.6.5 Ajexperience 404 Solution 1.6.6 Ajexperience 404 Solution 1.6.7 Ajexperience 404 Solution 1.7.0 Ajexperience 404 Solution 1.7.1 Ajexperience 404 Solution 1.7.2 Ajexperience 404 Solution 1.7.3 Ajexperience 404 Solution 1.7.4 Ajexperience 404 Solution 1.8.0 Ajexperience 404 Solution 1.8.1 Ajexperience 404 Solution 1.8.2 Ajexperience 404 Solution 1.9.0 Ajexperience 404 Solution 1.9.1 Ajexperience 404 Solution 1.9.2 Ajexperience 404 Solution 1.9.3 Ajexperience 404 Solution 2.0.0 Ajexperience 404 Solution 2.1.0 Ajexperience 404 Solution 2.1.1 Ajexperience 404 Solution 2.2.0 Ajexperience 404 Solution 2.2.1 Ajexperience 404 Solution 2.2.2 Ajexperience 404 Solution 2.3.0 Ajexperience 404 Solution 2.3.1 Ajexperience 404 Solution 2.3.2 Ajexperience 404 Solution 2.4.0 Ajexperience 404 Solution 2.4.1 Ajexperience 404 Solution 2.5.0 Ajexperience 404 Solution 2.5.1 Ajexperience 404 Solution 2.5.2 Ajexperience 404 Solution 2.5.3 Ajexperience 404 Solution 2.5.4 Ajexperience 404 Solution 2.6.0 Ajexperience 404 Solution 2.6.1 Ajexperience 404 Solution 2.6.2 Ajexperience 404 Solution 2.6.3 Ajexperience 404 Solution 2.6.4 Ajexperience 404 Solution 2.7.0 Ajexperience 404 Solution 2.8.0 Ajexperience 404 Solution 2.9.0 Ajexperience 404 Solution 2.9.1 Ajexperience 404 Solution 2.9.2 Ajexperience 404 Solution 2.9.3 Ajexperience 404 Solution 2.9.4 Ajexperience 404 Solution 2.9.5 Ajexperience 404 Solution 2.10.0 Ajexperience 404 Solution 2.10.1 Ajexperience 404 Solution 2.10.2 Ajexperience 404 Solution 2.10.3 Ajexperience 404 Solution 2.11.0 Ajexperience 404 Solution 2.11.1 Ajexperience 404 Solution 2.11.2 Ajexperience 404 Solution 2.12.0 Ajexperience 404 Solution 2.12.1 Ajexperience 404 Solution 2.12.2 Ajexperience 404 Solution 2.13.0 Ajexperience 404 Solution 2.14.0 Ajexperience 404 Solution 2.14.1 Ajexperience 404 Solution 2.15.0 Ajexperience 404 Solution 2.15.1 Ajexperience 404 Solution 2.15.2 Ajexperience 404 Solution 2.15.3 Ajexperience 404 Solution 2.15.4 Ajexperience 404 Solution 2.16.0 Ajexperience 404 Solution 2.16.2 Ajexperience 404 Solution 2.17.0 Ajexperience 404 Solution 2.17.1 Ajexperience 404 Solution 2.17.2 Ajexperience 404 Solution 2.18.0 Ajexperience 404 Solution 2.18.1 Ajexperience 404 Solution 2.18.2 Ajexperience 404 Solution 2.18.3 Ajexperience 404 Solution 2.18.4 Ajexperience 404 Solution 2.18.5 Ajexperience 404 Solution 2.18.6 Ajexperience 404 Solution 2.19.0 Ajexperience 404 Solution 2.19.1 Ajexperience 404 Solution 2.19.2 Ajexperience 404 Solution 2.19.3 Ajexperience 404 Solution 2.19.4 Ajexperience 404 Solution 2.19.5 Ajexperience 404 Solution 2.19.6 Ajexperience 404 Solution 2.20.0 Ajexperience 404 Solution 2.20.1 Ajexperience 404 Solution 2.20.2 Ajexperience 404 Solution 2.20.3 Ajexperience 404 Solution 2.20.4 Ajexperience 404 Solution 2.20.5 Ajexperience 404 Solution 2.21.0 Ajexperience 404 Solution 2.21.1 Ajexperience 404 Solution 2.21.2 Ajexperience 404 Solution 2.21.3 Ajexperience 404 Solution 2.21.6 Ajexperience 404 Solution 2.21.7 Ajexperience 404 Solution 2.21.8 Ajexperience 404 Solution 2.21.9 Ajexperience 404 Solution 2.21.10 Ajexperience 404 Solution 2.21.11 Ajexperience 404 Solution 2.21.12 Ajexperience 404 Solution 2.21.14 Ajexperience 404 Solution 2.21.15 Ajexperience 404 Solution 2.21.16 Ajexperience 404 Solution 2.21.17 Ajexperience 404 Solution 2.21.18 Ajexperience 404 Solution 2.21.19 Ajexperience 404 Solution 2.22.0 Ajexperience 404 Solution 2.22.1 Ajexperience 404 Solution 2.22.2 Ajexperience 404 Solution 2.22.3 Ajexperience 404 Solution 2.22.4 Ajexperience 404 Solution 2.22.5 Ajexperience 404 Solution 2.22.6 Ajexperience 404 Solution 2.22.7 Ajexperience 404 Solution 2.22.8 Ajexperience 404 Solution 2.22.9 Ajexperience 404 Solution 2.22.10 Ajexperience 404 Solution 2.22.11 Ajexperience 404 Solution 2.23.0 Ajexperience 404 Solution 2.23.1 Ajexperience 404 Solution 2.23.2 Ajexperience 404 Solution 2.23.3 Ajexperience 404 Solution 2.23.4 Ajexperience 404 Solution 2.23.5 Ajexperience 404 Solution 2.23.6 Ajexperience 404 Solution 2.23.7 Ajexperience 404 Solution 2.23.8 Ajexperience 404 Solution 2.23.9 Ajexperience 404 Solution 2.23.10 Ajexperience 404 Solution 2.23.11 Ajexperience 404 Solution 2.23.12 Ajexperience 404 Solution 2.23.13 Ajexperience 404 Solution 2.24.0 Ajexperience 404 Solution 2.24.1 Ajexperience 404 Solution 2.24.2 Ajexperience 404 Solution 2.24.3 Ajexperience 404 Solution 2.24.4 Ajexperience 404 Solution 2.24.5 Ajexperience 404 Solution 2.24.6 Ajexperience 404 Solution 2.24.7 Ajexperience 404 Solution 2.25.0 Ajexperience 404 Solution 2.25.1 Ajexperience 404 Solution 2.25.2 Ajexperience 404 Solution 2.25.3 Ajexperience 404 Solution 2.25.4 Ajexperience 404 Solution 2.25.5 Ajexperience 404 Solution 2.26.2 Ajexperience 404 Solution 2.26.3 Ajexperience 404 Solution 2.26.4 Ajexperience 404 Solution 2.26.6 Ajexperience 404 Solution 2.26.7 Ajexperience 404 Solution 2.27.0 Ajexperience 404 Solution 2.27.1 Ajexperience 404 Solution 2.27.2 Ajexperience 404 Solution 2.27.3 Ajexperience 404 Solution 2.27.4 Ajexperience 404 Solution 2.27.5 Ajexperience 404 Solution 2.27.6 Ajexperience 404 Solution 2.27.7 Ajexperience 404 Solution 2.27.8 Ajexperience 404 Solution 2.27.9 Ajexperience 404 Solution 2.27.10 Ajexperience 404 Solution 2.27.11 Ajexperience 404 Solution 2.27.12 Ajexperience 404 Solution 2.27.13 Ajexperience 404 Solution 2.27.14 Ajexperience 404 Solution 2.28.0 Ajexperience 404 Solution 2.28.1 Ajexperience 404 Solution 2.29.0 Ajexperience 404 Solution 2.29.1 Ajexperience 404 Solution 2.29.2 Ajexperience 404 Solution 2.29.3 Ajexperience 404 Solution 2.29.4 Ajexperience 404 Solution 2.30.0 Ajexperience 404 Solution 2.30.1 Ajexperience 404 Solution 2.30.2 Ajexperience 404 Solution 2.30.3 Ajexperience 404 Solution 2.30.4 Ajexperience 404 Solution 2.30.5 Ajexperience 404 Solution 2.30.6 Ajexperience 404 Solution 2.30.7 Ajexperience 404 Solution 2.30.8 Ajexperience 404 Solution 2.30.9 Ajexperience 404 Solution 2.30.10 Ajexperience 404 Solution 2.30.11 Ajexperience 404 Solution 2.30.12 Ajexperience 404 Solution 2.30.13 Ajexperience 404 Solution 2.30.14 Ajexperience 404 Solution 2.30.15 Ajexperience 404 Solution 2.30.16 Ajexperience 404 Solution 2.31.0 Ajexperience 404 Solution 2.31.1 Ajexperience 404 Solution 2.31.2 Ajexperience 404 Solution 2.31.3 Ajexperience 404 Solution 2.31.4 Ajexperience 404 Solution 2.31.5 Ajexperience 404 Solution 2.31.6 Ajexperience 404 Solution 2.31.7 Ajexperience 404 Solution 2.31.8 Ajexperience 404 Solution 2.31.9 Ajexperience 404 Solution 2.31.10 Ajexperience 404 Solution 2.31.11 Ajexperience 404 Solution 2.31.12 Ajexperience 404 Solution 2.31.13 Ajexperience 404 Solution 2.32.0 Ajexperience 404 Solution 2.32.1 Ajexperience 404 Solution 2.32.3 Ajexperience 404 Solution 2.33.0	221

Common Weakness Enumeration (CWE)

CWE-532 - Information Exposure Through Log Files

Common Attack Pattern Enumeration and Classification (CAPEC)

Fuzzing and observing application log data/errors for application mapping
An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. By observing logs and error messages, the attacker can learn details about the configuration of the target application and might be able to cause the target to disclose sensitive information.

References

https://patchstack.com/database/vulnerability/404-solution/wordpress-404-solution-plugin-2-33-0-sensitive-data-exposure-via-log-file-vulnerability?_s_id=cve