What is the severity of CVE-2024-1759?

CVE-2024-1759 has a high severity due to its potential for Stored Cross-Site Scripting attacks.

How do I fix CVE-2024-1759?

To fix CVE-2024-1759, update the WP ULike plugin to the latest version that addresses the vulnerability.

Who is affected by CVE-2024-1759?

CVE-2024-1759 affects all versions of the WP ULike plugin up to and including version 4.6.9 for WordPress.

What type of attack does CVE-2024-1759 enable?

CVE-2024-1759 enables Stored Cross-Site Scripting attacks through insufficient input sanitization of user display names.

Is authentication required to exploit CVE-2024-1759?

Yes, exploitation of CVE-2024-1759 requires authentication, as it targets authenticated users' display names.

Vulnerability/
CVE-2024-1759

medium

6.4

CWE

2/5/2024

4/6/2024

CVE-2024-1759: XSS

First published: Thu May 02 2024(Updated: )

The WP ULike – Most Advanced WordPress Marketing Toolkit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via a user's display name in all versions up to, and including, 4.6.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Credit: security@wordfence.com

Affected Software	Affected Version	How to fix
WP ULike	<=4.6.9

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-1759?
CVE-2024-1759 has a high severity due to its potential for Stored Cross-Site Scripting attacks.
How do I fix CVE-2024-1759?
To fix CVE-2024-1759, update the WP ULike plugin to the latest version that addresses the vulnerability.
Who is affected by CVE-2024-1759?
CVE-2024-1759 affects all versions of the WP ULike plugin up to and including version 4.6.9 for WordPress.
What type of attack does CVE-2024-1759 enable?
CVE-2024-1759 enables Stored Cross-Site Scripting attacks through insufficient input sanitization of user display names.
Is authentication required to exploit CVE-2024-1759?
Yes, exploitation of CVE-2024-1759 requires authentication, as it targets authenticated users' display names.

agent/references
agent/weakness
agent/description
agent/first-publish-date
agent/type
collector/nvd-api
source/NVD
agent/severity
agent/author
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
agent/softwarecombine
agent/tags
agent/guess-ai
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/wp ulike
canonical/wp ulike

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2024-1759?
CVE-2024-1759 has a high severity due to its potential for Stored Cross-Site Scripting attacks.
How do I fix CVE-2024-1759?
To fix CVE-2024-1759, update the WP ULike plugin to the latest version that addresses the vulnerability.
Who is affected by CVE-2024-1759?
CVE-2024-1759 affects all versions of the WP ULike plugin up to and including version 4.6.9 for WordPress.
What type of attack does CVE-2024-1759 enable?
CVE-2024-1759 enables Stored Cross-Site Scripting attacks through insufficient input sanitization of user display names.
Is authentication required to exploit CVE-2024-1759?
Yes, exploitation of CVE-2024-1759 requires authentication, as it targets authenticated users' display names.