CVE-2024-0555
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 · uneditedA Cross-Site Request Forgery (CSRF) vulnerability has been found on WIC1200, affecting version 1.1. An authenticated user could lead another user into executing unwanted actions inside the application they are logged in. This vulnerability is possible due to the lack of propper CSRF token implementation.
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 confidenceCSRF vulnerability in WIC1200 v1.1 allows an authenticated attacker to trick other logged-in users into unknowingly executing unintended actions due to missing anti-CSRF token validation on state-changing operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.1CVSS 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
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm firmware versionAccess the device web interface and navigate to System Settings, About, or Status page to view the firmware version. Alternatively, check the HTTP response headers or the login page source for version information.Affected if The firmware version is exactly 1.1
-
Identify state-changing operationsReview the application for forms, buttons, or API endpoints that perform actions like configuration changes, user management, device control, or settings modifications (POST, PUT, DELETE requests).Affected if The device has web-accessible state-changing functionality
-
Check for CSRF token presence in formsInspect the HTML source of state-changing forms (e.g., configuration save buttons, user add/delete) and look for a hidden input field containing a token value, or check if the form includes a token in the action URL.Affected if Forms lack a hidden CSRF token field or token parameter
-
Verify CSRF token in AJAX requestsIf the application uses JavaScript AJAX calls for state changes, inspect the request headers or payload to determine if a CSRF token, XSRF-token, or similar security token is included with each request.Affected if AJAX requests do not include CSRF tokens in headers or body
-
Test server-side token validationSubmit a state-changing request without a CSRF token (or with an invalid/tampered token) and observe if the server accepts or rejects the request. A successful submission without a valid token indicates missing protection.Affected if The server processes state-changing requests without validating a CSRF token
The environment is affected if the Wic1200 firmware is version 1.1 AND state-changing operations lack CSRF token validation on forms and AJAX requests.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement synchronizer token pattern: generate unique CSRF tokens per session or request, validate tokens server-side on all POST/PUT/DELETE endpoints, and include tokens in forms/ajax requests.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0555 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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