S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Feb 8, 2026

CVE-2024-13226 Scanner

CVE-2024-13226 Scanner - Cross-Site Scripting (XSS) vulnerability in A5 Custom Login Page

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.4k
Times Used
continuous scan runs
5.8k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2024-13226
6.1
CVSSmedium
Exploitable remotely over the internet · no authentication required · user interaction needed.

The A5 Custom Login Page WordPress plugin through 2.8.1 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

Attack Vector
Network
Privileges Req.
None
User Interaction
Required
Affected
A5 Custom Login Page
0
Updated Sep 10, 2026View on NVD →
Detail

A5 Custom Login Page is a WordPress plugin widely used by website administrators to customize their login pages, enhancing both aesthetics and user experience. This plugin is highly favored by WordPress sites and developers who aim to provide a branded login experience without altering the core WordPress files. The plugin is maintained by active developers ensuring that it remains updated with WordPress core changes. It is typically used by web developers, small businesses, and site owners who manage their own WordPress sites. However, like all plugins, it must be properly managed to avoid introducing vulnerabilities into the site. Regular updates and reviews are essential to ensure that vulnerabilities do not compromise the website.

The reflected Cross-Site Scripting (XSS) vulnerability in the A5 Custom Login Page occurs due to insufficient sanitization and escaping of user input. This vulnerability allows attackers to craft a URL that executes malicious scripts when viewed by a user with high privileges. Such attacks are most dangerous when targeting users with admin-level access, potentially allowing the attacker to hijack sessions or perform actions on behalf of the compromised user. This vulnerability relies on social engineering, where the victim must click a malicious link for the exploit to work. Due to its nature, it is critical for users to implement security measures such as input validation and sanitization. Resolving this issue is essential to maintain website and data integrity.

The technical details of the vulnerability indicate the presence of improper input handling in the plugin's settings page. If an input is not properly sanitized, an attacker can include arbitrary HTML or JavaScript in the output, which is executed in the context of the user's browser. The endpoint affected is typically a parameters page used for configuration, where a crafted script tag can be injected. Moreover, such scripts execute in the security context of the target website, allowing the capture of cookies or other sensitive information. The specific parameter affected lacks proper output encoding, facilitating the exploitation process. Addressing this involves employing standard sanitization libraries or techniques to escape potentially dangerous characters.

If exploited by malicious actors, this vulnerability could lead to severe consequences for affected websites. An attacker who successfully executes a cross-site scripting attack could impersonate high-privilege users, altering website content or decimating site functionality. Additionally, stolen session cookies could grant unauthorized access to admin areas or backends, leading to broader security breaches. This vulnerability could also be combined with other exploits, increasing the potential harm. Regular maintenance and adherence to security protocols are necessary to thwart any exploitation attempts. The risk underscores the importance of keeping plugins updated and scrutinizing any third-party code added to a site.

REFERENCES

Solution Advice
  • Implement proper input validation and sanitization measures to prevent script injection.
  • Apply updates released by the plugin developer to patch the vulnerability.
  • Conduct regular code reviews and security audits to detect similar issues early.
  • Educate users to avoid clicking unknown links and ensure they recognize potentially malicious inputs.
  • Consider employing a content security policy (CSP) to mitigate script execution risks.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.