dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-5676

MEDIUM · 6.8 CVSS v3.1 Published 2024-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Paradox IP150 Internet Module in version 1.40.00 is vulnerable to Cross-Site Request Forgery (CSRF) attacks due to a lack of countermeasures and the use of the HTTP method `GET` to introduce changes in the system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Paradox IP150 Internet Module version 1.40.00 is vulnerable to Cross-Site Request Forgery (CSRF) attacks. The application uses HTTP GET requests to perform state-changing operations (which violates HTTP semantics) and lacks anti-CSRF tokens or other countermeasures, allowing attackers to trick authenticated users into performing unintended actions.

MitigationImplement CSRF protection via anti-CSRF tokens and change state-changing operations from GET to POST/PUT methods. If vendor patch unavailable, deploy compensating controls such as network segmentation or a web application firewall with CSRF mitigation at the perimeter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the IP150 firmware version
    Access the Paradox IP150 web interface (typically at its IP address) and navigate to the status or about page to view the firmware version, or check the HTTP response headers for the version string
    Affected if The installed version is 1.40.00 or falls within the affected range starting at 1.40.00
  2. Verify the web interface uses HTTP GET for state-changing operations
    Log into the IP150 web interface as an authenticated user, then inspect the HTML source of pages containing configuration controls (e.g., arm/disarm, zone bypass, output control) and check if forms use method="GET" or if links trigger state changes via URL parameters
    Affected if State-changing actions (like arming/disarming, modifying zones, or controlling outputs) are performed via HTTP GET requests rather than POST/PUT
  3. Check for anti-CSRF tokens in requests
    Capture HTTP requests when performing actions in the IP150 web interface and inspect whether each request includes a CSRF token, anti-CSRF header, or unique session-bound parameter in the request body or headers
    Affected if Requests lack anti-CSRF tokens, unique session identifiers, or referer validation headers
  4. Confirm absence of request origin verification
    Send a state-changing request to the IP150 from an external origin (e.g., via curl from a different IP) or with a mismatched Origin/Referer header and observe if the request is processed without rejection
    Affected if The device accepts and processes state-changing requests without validating the request origin or referer header
  5. Test for CSRF vulnerability with authenticated session
    While authenticated to the IP150 web interface, click a malicious link or visit an external page containing a crafted GET request to the IP150 (e.g., for arming/disarming) and verify if the action executes without user consent
    Affected if Clicking a link or loading an external page can trigger unauthorized state changes on the IP150 device

A user is affected if the Paradox IP150 Internet Module version is 1.40.00 or within the affected range AND the web interface uses HTTP GET for state-changing operations without anti-CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF protection via anti-CSRF tokens and change state-changing operations from GET to POST/PUT methods. If vendor patch unavailable, deploy compensating controls such as network segmentation or a web application firewall with CSRF mitigation at the perimeter.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5676 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5676 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data