Ays Pro Quiz Maker Plugin up to 6.7.0.61 on WordPress information expsure

Summaryinfo

A vulnerability identified as problematic has been detected in Ays Pro Quiz Maker Plugin up to 6.7.0.61 on WordPress. The affected element is an unknown function. The manipulation leads to information expsure. This vulnerability is uniquely identified as CVE-2025-58015. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Ays Pro Quiz Maker Plugin up to 6.7.0.61 on WordPress. This issue affects some unknown functionality. The manipulation with an unknown input leads to a information expsure vulnerability. Using CWE to declare the problem leads to CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. Impacted is confidentiality. The summary by CVE is:

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Ays Pro Quiz Maker allows Retrieve Embedded Sensitive Data. This issue affects Quiz Maker: from n/a through 6.7.0.61.

The weakness was disclosed by Muhammad Zidan Ali Mansur. The advisory is shared at patchstack.com. The identification of this vulnerability is CVE-2025-58015 since 08/22/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• Ays Pro

Name

• Quiz Maker Plugin

Version

• 6.7.0.0
• 6.7.0.1
• 6.7.0.2
• 6.7.0.3
• 6.7.0.4
• 6.7.0.5
• 6.7.0.6
• 6.7.0.7
• 6.7.0.8
• 6.7.0.9
• 6.7.0.10
• 6.7.0.11
• 6.7.0.12
• 6.7.0.13
• 6.7.0.14
• 6.7.0.15
• 6.7.0.16
• 6.7.0.17
• 6.7.0.18
• 6.7.0.19
• 6.7.0.20
• 6.7.0.21
• 6.7.0.22
• 6.7.0.23
• 6.7.0.24
• 6.7.0.25
• 6.7.0.26
• 6.7.0.27
• 6.7.0.28
• 6.7.0.29
• 6.7.0.30
• 6.7.0.31
• 6.7.0.32
• 6.7.0.33
• 6.7.0.34
• 6.7.0.35
• 6.7.0.36
• 6.7.0.37
• 6.7.0.38
• 6.7.0.39
• 6.7.0.40
• 6.7.0.41
• 6.7.0.42
• 6.7.0.43
• 6.7.0.44
• 6.7.0.45
• 6.7.0.46
• 6.7.0.47
• 6.7.0.48
• 6.7.0.49
• 6.7.0.50
• 6.7.0.51
• 6.7.0.52
• 6.7.0.53
• 6.7.0.54
• 6.7.0.55
• 6.7.0.56
• 6.7.0.57
• 6.7.0.58
• 6.7.0.59
• 6.7.0.60
• 6.7.0.61

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion