CVE-2023-35134
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 · uneditedWeintek Weincloud v0.13.6 could allow an attacker to reset a password with the corresponding account’s JWT token only.
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 · moderate confidenceWeintek Weincloud v0.13.6 has an improper authentication vulnerability in its password reset function. The system incorrectly allows password changes using only a valid JWT token for the corresponding account, without requiring additional verification such as the current password, email confirmation, or secondary authentication factors. This enables account takeover if an attacker obtains a user's JWT token.
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= 0.13.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Weintek Weincloud installationLocate the Weincloud application installation directory or check running services on the host system. Look for executable files, services, or containers named 'weincloud' or 'Weincloud'. Check system services list if running as a daemon.Affected if The product is not Weintek Weincloud, or Weincloud is not installed on the system.
-
Determine installed Weincloud versionCheck the version of the installed Weincloud instance. Common methods include: viewing the 'about' or 'version' page in the web interface, checking the executable file version properties, reviewing installation logs, or querying the API endpoint for version information if available.Affected if The installed version is not exactly 0.13.6.
-
Verify password reset function is accessibleConfirm that the password reset functionality is enabled and accessible in the Weincloud instance. This may involve checking if the '/password-reset' or similar endpoint responds in the web application, or verifying the feature is not disabled in configuration files.Affected if The password reset function is not present or is disabled in the deployment.
-
Confirm JWT-based authentication is in useInspect the authentication mechanism by examining session tokens after login. JWT tokens typically appear as Base64-encoded strings in browser developer tools under Application/Storage tabs or Authorization headers. Check if the application uses JWT tokens for maintaining authenticated sessions.Affected if JWT tokens are not being used for authentication in the Weincloud instance.
You are affected if Weintek Weincloud version 0.13.6 is installed, the password reset function is accessible, and JWT-based authentication is in use, allowing password changes with only a valid JWT token.
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 multi-factor verification in the password reset flow requiring additional proof of identity beyond just a valid JWT token, such as email confirmation links, security questions, or step-up authentication.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35134 — 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-2023-35134 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