CVE-2024-11366 json
SEO Landing Page Generator <= 1.66.2 - Reflected Cross-Site Scripting
published 2024-11-28 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-34032
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
The SEO Landing Page Generator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.66.2. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- intellasoftsolutions SEO Landing Page Generator
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/99dcb6c4-b9c6-4d3d-942f-b3877cc3efa7?source=cve
- plugins.trac.wordpress.org /browser/seo-landing-page-generator/trunk/admin/class-issslpg-admin-location-settings-page.php#L185
- plugins.trac.wordpress.org /browser/seo-landing-page-generator/trunk/admin/class-issslpg-admin-location-settings-page.php#L330
- plugins.trac.wordpress.org /browser/seo-landing-page-generator/trunk/admin/class-issslpg-admin-location-settings-page.php#L433
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3197642%40seo-landing-page-generator&new=3197642%40seo-landing-
Sources
- CVE List CVE-2024-11366
- NVD CVE-2024-11366
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.