dbcve.org
Hr PortalApplication · Scshr

CVE-2023-34357

HIGH · 7.8 CVSS v3.1 Published 2023-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Soar Cloud Ltd. HR Portal has a weak Password Recovery Mechanism for Forgotten Password. The reset password link sent out through e-mail, and the link will remain valid after the password has been reset and after the expected expiration date. An attacker with access to the browser history or has the line can thus use the URL again to change the password in order to take over the account.

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 HR Portal's password reset mechanism fails to invalidate the reset token after successful password reset and after the expected expiration date passes. This allows an attacker with access to the reset URL (via browser history or network interception) to reuse the same link indefinitely to reset the password and take over the account.

MitigationImplement proper token lifecycle management: invalidate the reset token immediately upon successful password reset and enforce time-based expiration. Additionally, generate a new unique token for each reset request and store its used/invalidated state server-side.

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
Hr PortalApplication
Affected:= 7.3.2023.0510= 7.3.2023.0705

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

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check installed HR Portal version
    Access the HR Portal's system information page, check the about/help section, or query the application's version endpoint. Common paths include /about, /system/info, or the admin dashboard.
    Affected if The installed version matches 7.3.2023.0510 or 7.3.2023.0705 exactly
  2. Verify password reset feature is accessible
    Navigate to the login page and confirm the password reset/forgot password function is available and enabled for end users.
    Affected if Password reset functionality is enabled and accessible to users
  3. Test token invalidation after password change
    Initiate a password reset for a test account, complete the reset process with a new password, then attempt to use the original reset token link again to reset the password a second time.
    Affected if The same reset token works a second time after the password was already successfully changed (token was not invalidated)
  4. Test token expiration enforcement
    After the expected token expiration window passes (check application documentation for the configured duration), attempt to use an unused reset token to reset the password.
    Affected if The expired reset token still successfully allows password reset (expiration is not enforced)
  5. Inspect token lifecycle configuration
    Review server-side configuration files or database settings related to password reset token lifecycle: token validity duration, storage of token used/invalidated state, and token uniqueness enforcement.
    Affected if No token expiration timeout is configured, or tokens are not marked as used/invalidated in the database after successful reset

You are affected if the installed version is 7.3.2023.0510 or 7.3.2023.0705 AND the password reset feature is enabled AND either used tokens remain valid or expired tokens continue to work.

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 proper token lifecycle management: invalidate the reset token immediately upon successful password reset and enforce time-based expiration. Additionally, generate a new unique token for each reset request and store its used/invalidated state server-side.

Fix this in Hr Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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 locally
dbcve dependency scanner

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