CVE-2023-40761
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 · uneditedUser enumeration is found in PHPJabbers Yacht Listing Script v2.0. This issue occurs during password recovery, where a difference in messages could allow an attacker to determine if the user is valid or not, enabling a brute force attack with valid users.
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 password recovery function in PHPJabbers Yacht Listing Script v2.0 reveals different error messages for existing versus non-existing user accounts, allowing attackers to enumerate valid usernames through the password reset functionality and subsequently launch brute force attacks.
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.0CVSS 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 the installed version of PHPJabbers Yacht Listing ScriptCheck the version file (often version.php or similar in the root/includes directory), the admin panel 'About' page, or any version string in the source code headersAffected if The installed version is 2.0 exactly, as this is the only affected version listed
-
Locate the password recovery functionalityAccess the password reset page - typically found at /index.php?controller=pjPassword or /password-reset/ on the frontend, or through the login page linkAffected if The password recovery page is accessible and functional on the affected version
-
Test with a non-existing username/emailSubmit a fake or non-existent email address/username to the password recovery form and record the exact error message or response shownAffected if A specific error message like 'User not found' or 'Email does not exist' is returned, revealing the account doesn't exist
-
Test with an existing username/emailSubmit a known-valid email address/username (e.g., an admin account) to the password recovery form and record the exact error message or response shownAffected if A different error message like 'Password reset instructions sent' or 'User found' is returned, confirming the account exists
-
Compare the error message responsesReview both responses from steps 3 and 4 - if they differ in content, timing, or any measurable way, the vulnerability is presentAffected if The application returns different messages for existing vs non-existing accounts, enabling user enumeration
A user is affected if they are running PHPJabbers Yacht Listing Script version 2.0 AND the password recovery function returns distinguishable messages for valid vs invalid accounts.
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 dataModify the password recovery mechanism to return identical messages regardless of whether the provided email/username exists in the system, preventing user enumeration.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40761 — 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-40761 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