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

CVE-2024-4600

HIGH · 7.1 CVSS v3.1 Published 2024-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Cross-Site Request Forgery vulnerability in Socomec Net Vision, version 7.20. This vulnerability could allow an attacker to trick registered users into performing critical actions, such as adding and updating accounts, due to lack of proper sanitisation of the ‘set_param.cgi’ file.

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

Cross-Site Request Forgery (CSRF) vulnerability in Socomec Net Vision version 7.20's set_param.cgi file. The lack of proper request sanitization allows attackers to craft malicious HTML or scripts that trick authenticated users into unknowingly submitting requests that perform critical operations such as adding or modifying user accounts.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations in set_param.cgi, validate Origin and Referer headers on POST requests, and configure SameSite cookie attributes to prevent cross-site request forgery.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 Socomec Net Vision version
    Access the Net Vision admin interface or check system documentation to locate the installed software version. Look for version information in the web UI footer, about page, or system info section.
    Affected if The installed version is 7.20 specifically, or falls within an unknown range around 7.20 if additional affected versions are discovered.
  2. Locate set_param.cgi file
    Check if the set_param.cgi script exists in the web root or CGI-bin directory of the Net Vision installation. Attempt to access it via HTTP GET or POST request to the known endpoint (typically /cgi-bin/set_param.cgi or similar).
    Affected if The set_param.cgi file is present and accessible on the target system.
  3. Verify CSRF token implementation
    Inspect the HTML source of forms that perform sensitive operations (user account management) in the Net Vision interface. Check if each form includes a hidden input field containing a unique anti-CSRF token, and verify that the server validates this token on submission.
    Affected if Forms in set_param.cgi do not contain anti-CSRF tokens, or tokens are not validated server-side.
  4. Check Origin and Referer header validation
    Submit a POST request to set_param.cgi from an external or unauthorized Origin header (e.g., using curl with -H 'Origin: http://evil.com'). Observe whether the server rejects the request or accepts it without validation.
    Affected if The server accepts requests with arbitrary or mismatched Origin/Referer headers without rejecting them.
  5. Inspect SameSite cookie attributes
    Capture authentication cookies using browser developer tools or a proxy. Examine the Set-Cookie headers to determine if the SameSite attribute is set to 'Strict' or 'Lax', or if it is missing entirely.
    Affected if Authentication cookies lack SameSite attributes or are set to 'None' without Secure flags.

A user is affected if running Socomec Net Vision version 7.20 with the set_param.cgi endpoint accessible and without proper CSRF protections (anti-CSRF tokens, Origin/Referer validation, and SameSite cookies) in place.

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 anti-CSRF tokens (synchronizer token pattern) for all state-changing operations in set_param.cgi, validate Origin and Referer headers on POST requests, and configure SameSite cookie attributes to prevent cross-site request forgery.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4600 — 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-4600 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