> For the complete documentation index, see [llms.txt](https://docs.offsecguy.com/cve/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.offsecguy.com/cve/hr-performance-solutions/vulnerability/reflected-xss-current-goals.md).

# Reflected XSS - Current Goals

## Reflected XSS (authenticated)  <a href="#finding1" id="finding1"></a>

Performance Pro v3.19.17 and earlier is affected by multiple Stored Cross-Site Scripting (XSS) vulnerabilities (Persistent/Type II) via POST requests to:

{% hint style="warning" %}
`/index.php?mode=mGoalSetup&job=update&id=<goal_id>`
{% endhint %}

### Description

The application is vulnerable to multiple instances of stored (persistent) XSS in the Current Goals functionality. Malicious input provided by an authenticated user is stored server-side and later rendered into the DOM without proper encoding or sanitization. This allows execution of arbitrary JavaScript in the context of any user viewing the affected pages.

## **Affected Endpoints and Parameters:**

**Input (create/update goal):**\
Vulnerable fields:

* Goal Name
* Goal Notes (name field)
* Action Step Name
* Notes Name

**Reflected when viewing/printing goals:**\
`GET /viewgoals.php?printview=1&type=current`\
Vulnerable fields:

* Goal Name
* Goal Description
* Action Step Description

{% hint style="danger" %}
This vulnerability allows attackers to execute malicious scripts, alter the user's interface, and potentially redirect users to malicious sites.
{% endhint %}

***

### Exploitation

* Inject malicious javascript into any of the following input fields for current goals.&#x20;
  * Goal Name
  * Goal Description
  * Action Steps Name
  * Action Steps Description
  * Note Name
* **Send** the crafted URL to a victim via phishing, social engineering, or any other attack vector.
* When the victim navigates to the modified URL, the application reflects the malicious input directly into the browser without sufficient sanitization.
* **The victim’s browser renders the injected payload** in the error message, allowing arbitrary script execution within the victim's browser.

### Example 1 - XSS in Updating/Creating Current Goals

* Any of the highlighted fields are vulnerable to XSS between the Update/Creation\
  ![](/files/iW1CDD5DAX4tG04vV1IP)<br>
* Action Steps injection\
  ![](/files/R2mGfqDzlADAzgdeB0gY)
* Notes injection\
  ![](/files/6uosMDPhBVrJAZgCxYJP)
* Successful XSS exploitation\
  ![](/files/pXgmyXlLPagUQpsbRwDq)

Example 2 - XSS in View/Print of Current Goals

* Any of the highlighted fields are vulnerable to XSS in the View/Print URL\
  ![](/files/L2LkwdzvbTeCDorM6MCi)
* Successful XSS exploitation\
  ![](/files/tbmgreLR9RDV3mkaLHAp)
