CVE-2022-36565
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 · uneditedIncorrect access control in the install directory (C:\Wamp64) of Wamp v3.2.6 and below allows authenticated attackers to execute arbitrary code via overwriting binaries located in the directory.
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 confidenceWampServer v3.2.6 and below has incorrect file system access controls on its installation directory (C:\Wamp64). Authenticated users with standard privileges can overwrite executable binaries in this directory, leading to arbitrary code execution with the privileges of the Wamp service or when the binaries are next invoked.
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<= 3.2.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WampServer installation existsCheck if the C:\Wamp64 directory exists, or search for WampServer installation in common locations like C:\wamp64, C:\wamp, or the installation path specified during setup. Use 'dir C:\Wamp64' in Command Prompt or File Explorer.Affected if The C:\Wamp64 directory exists on the system (indicating WampServer is installed)
-
Determine installed WampServer versionLocate the wampmanager.exe file in the WampServer installation directory (e.g., C:\Wamp64\wampmanager.exe). Right-click the file, select Properties, and check the Details tab for the version number. Alternatively, look for a version file in the installation directory.Affected if The version number is 3.2.6 or lower, or if version information cannot be obtained but WampServer is present
-
Examine write permissions on the Wamp installation directoryRight-click the WampServer installation folder (e.g., C:\Wamp64), select Properties, go to the Security tab, and review the permissions for Users, Everyone, and other standard user groups. Check if any non-admin accounts or groups have Write or Modify permissions.Affected if Standard users (non-admin accounts) or the Users group have Write or Modify permissions on the C:\Wamp64 directory
-
Verify executable binaries are world-writableCheck specific executable files in the installation directory (such as wampmanager.exe, apache/bin/*.exe, or php/*.exe) by viewing their security permissions. Confirm if users with standard privileges can modify these files.Affected if Users with standard (non-elevated) privileges can overwrite executable binaries in the WampServer installation directory
-
Check WampService account privilegesOpen Services (services.msc), locate the Wampapache or Wampmysqld services, right-click and select Properties. Note the account under which the service runs (often LocalSystem or a specific user account).Affected if The WampServer services run with elevated privileges (such as LocalSystem or Administrator) and the directory permissions allow standard users to write files
A user is affected if WampServer version 3.2.6 or lower is installed AND the installation directory grants Write or Modify permissions to standard (non-admin) users, allowing them to replace executable binaries.
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 dataRestrict write permissions on the Wamp installation directory to only trusted administrators; remove world/group write access and ensure the Wamp service runs with minimal required privileges. Audit directory permissions and remove any unnecessary write access.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36565 — 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-2022-36565 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