invoicing Payments Plugin GetPaid 2.4.6 on WordPress Help Text cross site scripting

Summaryinfo

A vulnerability identified as problematic has been detected in invoicing Payments Plugin GetPaid 2.4.6 on WordPress. This impacts an unknown function. The manipulation of the argument Help Text leads to cross site scripting. This vulnerability is referenced as CVE-2021-47948. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability was found in invoicing Payments Plugin GetPaid 2.4.6 on WordPress and classified as problematic. This issue affects some unknown functionality. The manipulation of the argument Help Text with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity. The summary by CVE is:

WordPress GetPaid Plugin 2.4.6 contains an HTML injection vulnerability that allows authenticated attackers to inject arbitrary HTML code by exploiting the Help Text field in payment forms. Attackers can inject malicious HTML including image tags and scripts into the Help Text field during payment form creation, which gets stored in the database and executed in the browser when the form is viewed.

The weakness was published by Niraj Mahajan as 50246. The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2021-47948 since 02/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

The exploit is available at exploit-db.com. It is declared as proof-of-concept.

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

The vulnerability is also documented in the vulnerability database at Exploit-DB (50246). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• invoicing

Name

• Payments Plugin GetPaid

Version

• 2.4.6

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