CVE-2024-29836
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 · uneditedThe Web interface of Evolution Controller Versions 2.04.560.31.03.2024 and below contains poorly configured access control, allowing for an unauthenticated attacker to update and add user profiles within the application, and gain full access of the site.
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 confidenceThe Evolution Controller web interface versions 2.04.560.31.03.2024 and below contains a broken access control vulnerability that allows unauthenticated attackers to directly access user profile management functions. Due to missing or inadequate authorization checks on sensitive endpoints, an attacker can create new user accounts or modify existing ones, potentially escalating privileges to administrator-level access and gaining full site control.
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<= 2.04.560CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify Evolution Controller versionCheck the software version displayed in the Evolution Controller web interface login page header, or query the server for version information via the application's built-in 'About' or 'System Info' page typically found at /about or /system/status endpoints.Affected if Version number is 2.04.560 or lower (e.g., 2.04.560.31.03.2024, 2.04.500, etc.)
-
Locate user profile management endpointsReview the application's URL structure for endpoints related to user management such as /user, /users, /profile, /user/add, /user/edit, /admin/user, /api/users, or similar paths that handle account creation or modification.Affected if These endpoints exist in the web application
-
Test unauthenticated access to user creationSend an HTTP GET or POST request to the identified user creation endpoint (e.g., /user/add or /api/users/create) without providing any authentication credentials or session cookie.Affected if The request is accepted and returns a user creation form or success response rather than redirecting to a login page or returning 401/403
-
Test unauthenticated access to user modificationSend an HTTP request to an existing user modification endpoint (e.g., /user/edit?id=1 or /admin/user/update) without any authentication tokens.Affected if The endpoint displays user details or allows modification without requiring login credentials
-
Verify authorization enforcement on sensitive endpointsIntercept an authenticated session, then attempt to access user management functions using the same session token on a different browser or incognito window without re-authenticating.Affected if The application permits access to administrative user functions without re-validating credentials or returns user data without proper authorization checks
A defender is affected if the Evolution Controller version is 2.04.560 or lower AND user profile management endpoints are accessible without any authentication credentials.
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 proper authentication and role-based authorization checks on all user profile management endpoints, ensuring that unauthenticated requests are rejected and only authorized users can modify profiles. Apply the vendor patch as soon as available.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29836 — 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-29836 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