Security weakness
CWE-765 Multiple Unlocks of a Critical Resource
A base-level weakness that can lead to data, pages or code changed and downtime and lost sales. Here is what it is, what it can cost you and how to close it.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-765?
Multiple Unlocks of a Critical Resource: The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.
Business impact
What CWE-765 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Integrity
Data, pages or code changed
Prices, orders, content or the code your site runs can be altered without your approval.
- DoS: Crash, Exit, or Restart
- Modify Memory
- Unexpected State
Availability
Downtime and lost sales
Crashes, slowdowns or exhausted resources can take your site, store or app offline.
- DoS: Crash, Exit, or Restart
- Modify Memory
- Unexpected State
Free security check
Is CWE-765 hiding in your site?
A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.
Official definition
How MITRE defines CWE-765
Multiple Unlocks of a Critical Resource
The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.
Prevention
How to fix CWE-765, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Implementation
- When locking and unlocking a resource, try to be sure that all control paths through the code in which the resource is locked one or more times correspond to exactly as many unlocks. If the product acquires a lock and then determines it is not able to perform its intended behavior, be sure to release the lock(s) before waiting for conditions to improve. Reacquire the lock(s).
Detection and evidence
How CWE-765 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.
Real vulnerabilities it caused
- CVE-2009-0935Attacker provides invalid address to a memory-reading function, causing a mutex to be unlocked twice
How we fix it
From finding to fixed: how Codefreex closes CWE-765
Scan and confirm
We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.
Fix at the source
We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.
Verify the fix
We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
Related weaknesses
Weaknesses related to CWE-765
FAQ
CWE-765: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
What is CWE-765?
CWE-765, “Multiple Unlocks of a Critical Resource”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.
How serious is CWE-765?
It can affect availability, integrity, with impacts such as dos: crash, exit, or restart, modify memory, unexpected state. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-765?
When locking and unlocking a resource, try to be sure that all control paths through the code in which the resource is locked one or more times correspond to exactly as many unlocks. If the product acquires a lock and then determines it is not able to perform.
Can Codefreex check my site for CWE-765?
Yes. A senior engineer reviews your site, store or app for CWE-765 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.
Free security check
Find out if CWE-765 affects your site
Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.
- A senior strategist reviews your request, not a sales bot
- Clear scope, timeline and estimate within one business day
- Free 30-minute discovery call, no obligation
- NDA available on request
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.