Skip to main content
CVE-2024-45986VulnerabilityPublished

CVE-2024-45986: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% 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 26 Sep 2024

  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 2026-10-25.

What to do

AI-suggested

To mitigate CVE-2024-45986, organizations should implement strict input validation and output encoding on all user-supplied data, especially during account registration and when displaying account information on voter.php and profile.php pages. Employing a Content Security Policy (CSP) can help reduce the impact of injected scripts. Restricting account registration to verified users or implementing CAPTCHA challenges can reduce the risk of automated malicious registrations. Regular security code reviews and penetration testing focused on XSS vulnerabilities are recommended. If possible, isolate user-generated content from sensitive application contexts using sandboxing or iframe techniques. Monitoring logs for unusual account registrations or script execution attempts can provide early detection. Since no official patches are available, organizations should consider applying custom fixes or workarounds to sanitize inputs and outputs until an official update is released. Educating users about the risks of clicking suspicious links or interacting with untrusted content within the voting system can also reduce exploitation likelihood.

Description

A stored Cross-Site Scripting (XSS) vulnerability was identified in Projectworld Online Voting System 1.0 that occurs when an account is registered with a malicious javascript payload. The payload is stored and subsequently executed in the voter.php and profile.php pages whenever the account information is accessed.

References

Community reviews

Loading reviews…