CVE-2023-36134
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 · uneditedIn PHP Jabbers Class Scheduling System 1.0, lack of verification when changing an email address and/or password (on the Profile Page) allows remote attackers to take over accounts.
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 confidenceThe PHP Jabbers Class Scheduling System 1.0 contains an IDOR (Insecure Direct Object Reference) vulnerability on the Profile Page where changing an email address and/or password lacks proper verification. An unauthenticated remote attacker can potentially manipulate profile parameters to take over existing user accounts without requiring the current password or email verification.
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.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.
-
Verify the PHP Jabbers Class Scheduling System versionLocate and inspect the installed version of the application - check version files, headers in PHP source files, or the admin dashboard about/information pageAffected if The installed version is 1.0
-
Confirm profile page is accessibleAccess the user profile modification page in the application - typically found at paths like /profile, /account, or /settings depending on the URL routingAffected if The profile modification page loads and accepts user input
-
Test for missing authorization on profile updatesSubmit a profile update request (email or password change) and observe whether the application validates that the request originates from the authenticated user account being modifiedAffected if Profile modifications can be submitted without proper user ownership verification or session validation
-
Check for IDOR vulnerability in profile parametersAttempt to manipulate user identifier parameters (such as user_id, id, or similar) in profile update requests to see if another user's profile can be modifiedAffected if The application accepts and processes profile changes for arbitrary user identifiers without additional verification
You are affected if you are running PHP Jabbers Class Scheduling System version 1.0 and the profile modification functionality is accessible without proper session-based authorization checks that verify the authenticated user matches the profile being modified.
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 current password verification before allowing email or password changes, add email confirmation links for address modifications, and enforce proper session-based authorization checks to ensure users can only modify their own profiles.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36134 — 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-36134 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