Security weakness
CWE-757 Selection of Less-Secure Algorithm During Negotiation
A class-level weakness that can lead to accounts and admin areas exposed. 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-757?
Selection of Less-Secure Algorithm During Negotiation: A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used in a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
Business impact
What CWE-757 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Access Control
Accounts and admin areas exposed
Logins and permission checks can be bypassed, putting admin and customer accounts at risk.
- Bypass Protection Mechanism
Free security check
Is CWE-757 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-757
Selection of Less-Secure Algorithm During Negotiation
A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used in a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
Also known as: Algorithm Downgrade
Detection and evidence
How CWE-757 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-2006-4302Attacker can select an older version of the software to exploit its vulnerabilities.
- CVE-2006-4407Improper prioritization of encryption ciphers during negotiation leads to use of a weaker cipher.
- CVE-2005-2969Chain: SSL/TLS implementation disables a verification step (CWE-325) that enables a downgrade attack to a weaker protocol.
- CVE-2001-1444Telnet protocol implementation allows downgrade to weaker authentication and encryption using an Adversary-in-the-Middle AITM attack.
- CVE-2002-1646SSH server implementation allows override of configuration setting to use weaker authentication schemes. This may be a composite with CWE-642.
How we fix it
From finding to fixed: how Codefreex closes CWE-757
- 01
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.
- 02
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.
- 03
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.
- 04
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
FAQ
CWE-757: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
What is CWE-757?
CWE-757, “Selection of Less-Secure Algorithm During Negotiation”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used in a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
How serious is CWE-757?
It can affect access control, with impacts such as bypass protection mechanism. The real risk depends on where the weakness sits and what data or functions it exposes.
Can Codefreex check my site for CWE-757?
Yes. A senior engineer reviews your site, store or app for CWE-757 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-757 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.