Skip to main content
VulnerabilityPublished Updated

CVE-2024-10033: aap-gateway · Cross-site Scripting

Affects aap-gatewaySource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Oct 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmaap-gatewaypkg:npm/aap-gatewayOther threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-10033, organizations should implement strict input validation and output encoding on the "?next=" URL parameter to ensure that injected scripts cannot execute. Employing a Content Security Policy (CSP) can help restrict the execution of unauthorized scripts. Web application firewalls (WAFs) can be configured to detect and block suspicious URL patterns exploiting this parameter. User education on the risks of clicking unknown or suspicious links is essential to reduce successful exploitation. Monitoring logs for unusual redirect patterns or script injection attempts can provide early detection. If possible, update or patch the aap-gateway component once official fixes become available. In the interim, consider disabling or restricting the use of the vulnerable parameter or implementing server-side checks to sanitize input. Additionally, ensure secure cookie attributes (HttpOnly, Secure, SameSite) are set to reduce session theft risk. Regular security assessments and penetration testing focusing on XSS vulnerabilities should be conducted to identify and remediate similar issues.

Description

A vulnerability was found in aap-gateway. A Cross-site Scripting (XSS) vulnerability exists in the gateway component. This flaw allows a malicious user to perform actions that impact users by using the "?next=" in a URL, which can lead to redirecting, injecting malicious script, stealing sessions and data.

References

Community reviews

Loading reviews…