sales@hackhalt.com

Home / Threats / CVE-2024-0708

Landing Page Cat - Information Disclosure (CVE-2024-0708)

CVE-2024-0708

The Landing Page Cat – Coming Soon Page, Maintenance Page & Squeeze Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.7.2. This makes it possible for unauthenticated attackers to access landing pages that may not be public.

CVE-2024-0708

MEDIUM CVSS 5.3 Published 2024-02-15 Updated 2025-01-23
AI Risk Elevated (60/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected Components 2
Reference Links 2
AI Risk Engine Elevated (60/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2024-02-15 CVE published and first recorded in the threat feed.
  2. 2025-01-23 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 153 days ago

AI enriched 153 days ago (2026-04-09 09:54 UTC)

Technical Summary

The Landing Page Cat – Coming Soon Page, Maintenance Page & Squeeze Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.7.2. This makes it possible for unauthenticated attackers to access landing pages that may not be public.

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Landing Page Cat PLUGIN · landing-page-cat Affected: < 1.7.3 Fixed in: 1.7.3
Squeeze Pages PLUGIN · squeeze-pages Affected range not specified Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Landing Page Cat to 1.7.3 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Restrict REST API in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require authentication for REST namespaces that do not need to be public, so the API cannot be used to enumerate content and accounts.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Landing Page Cat, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Landing Page Cat. Versions below 1.7.3 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Landing Page Cat to version 1.7.3 or later. That is the complete fix. Until you can update, Restrict REST API in Hack Halt Pro contains this class of attack at the request layer.

What can an attacker actually do?

This is a Information Disclosure flaw. An attacker who exploits it can read data they were never meant to see, which is often the first step in a larger attack.