Powie WHOIS Domain Check 0.9.31 Setting pwhois_settings.php cross site scripting

Summaryinfo

A vulnerability marked as problematic has been reported in Powie WHOIS Domain Check 0.9.31. Affected is an unknown function of the file pwhois_settings.php of the component Setting Handler. Performing a manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2020-37225. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Powie WHOIS Domain Check 0.9.31. This affects an unknown code of the file pwhois_settings.php of the component Setting Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

Powie's WHOIS Domain Check 0.9.31 contains a persistent cross-site scripting vulnerability that allows authenticated attackers to inject arbitrary JavaScript by exploiting unsanitized input fields in plugin settings. Attackers can submit malicious payloads through textarea and input elements in the pwhois_settings.php configuration page to execute JavaScript in the admin context and escalate privileges.

The weakness was shared by mqt as 48656. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2020-37225 since 05/13/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:pwhois_settings.php it is possible to find vulnerable targets with Google Hacking.

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

Vendor

• Powie

Name

• WHOIS Domain Check

Version

• 0.9.31

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