Skip to main content
VulnerabilityPublished Updated

CVE-2022-37137: Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =3.3
Fixed in–

AI-suggested

Organizations should immediately audit their use of PayMoney 3.3 or related ticketing systems for this vulnerability. Employ Content Security Policy (CSP) headers to restrict script execution sources in browsers. Limit user privileges to the minimum necessary to reduce the risk of exploitation (principle of least privilege). Educate users to recognize suspicious ticket content and avoid clicking on unexpected links or executing scripts. Monitor logs for unusual activity related to ticket replies and views. If possible, isolate the ticketing system from other critical infrastructure to contain potential breaches. Finally, maintain vigilance for vendor updates or patches and apply them promptly once available.

Description

PayMoney 3.3 is vulnerable to Stored Cross-Site Scripting (XSS) during replying the ticket. The XSS can be obtain from injecting under "Message" field with "description" parameter with the specially crafted payload to gain Stored XSS. The XSS then will prompt after that or can be access from the view ticket function.

References

Community reviews

Loading reviews…