CVE-2026-40043
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 · uneditedPachno 1.0.6 contains an authentication bypass vulnerability in the runSwitchUser() action that allows authenticated low-privilege users to escalate privileges by manipulating the original_username cookie. Attackers can set the client-controlled original_username cookie to any value and request a switch to user ID 1 to obtain session tokens or password hashes belonging to administrator 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 · high confidencePachno 1.0.6 has an authentication bypass in the runSwitchUser() action where authenticated low-privilege users can manipulate the client-controlled original_username cookie to switch to user ID 1, gaining access to administrator session tokens or password hashes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Confirm Pachno installationIdentify if Pachno is installed in your environment by checking for Pachno-related files, directories, or servicesAffected if Pachno is not installed - not affected
-
Check Pachno versionLocate and read the version file or configuration that stores the Pachno version number (commonly in version.php, a config file, or composer.json in the installation root)Affected if Version is 1.0.6 - potentially affected; versions different from 1.0.6 are not affected by this specific CVE
-
Verify runSwitchUser endpoint accessibilityCheck if the runSwitchUser action is accessible by reviewing the application routing or attempting to access the relevant URL endpoint (typically index.php with action=runSwitchUser or similar routing pattern)Affected if The endpoint is accessible to authenticated users without admin privileges - vulnerable configuration present
-
Inspect cookie handling for original_usernameReview the runSwitchUser() function code to determine if the original_username cookie value is used directly without server-side validation or authorization checksAffected if The cookie value is trusted and used directly for user switching - vulnerable
-
Test for privilege escalation via cookie manipulationAs a low-privilege authenticated user, attempt to modify the original_username cookie value to target user ID 1 and trigger the switch actionAffected if Successful switch to admin-level account is possible - confirmed affected
If running Pachno version 1.0.6 and the runSwitchUser action uses the original_username cookie without proper server-side authorization, the environment is affected by this authentication bypass.
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 dataFix the runSwitchUser() function to enforce proper server-side authorization checks and remove trust in cookie values for user identity; validate that the requesting user has permission to switch to the target account.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40043 — 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-2026-40043 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