Security weakness
CWE-620 Unverified Password Change
A base-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-620?
Unverified Password Change: When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
Business impact
What CWE-620 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
- Gain Privileges or Assume Identity
Free security check
Is CWE-620 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-620
Unverified Password Change
When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
Prevention
How to fix CWE-620, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Architecture and Design
- When prompting for a password change, force the user to provide the original password in addition to the new password.
- Do not use "forgotten password" functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the legitimate user already provided in the past; do not allow the current user to change this identity information until the correct password has been provided.
Detection and evidence
How CWE-620 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
Real vulnerabilities it caused
- CVE-2025-4903Router web interface allows unverified password change
- CVE-2007-0681Web app allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions.
- CVE-2000-0944Web application password change utility doesn’t check the original password.
How we fix it
From finding to fixed: how Codefreex closes CWE-620
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-620
FAQ
CWE-620: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
What is CWE-620?
CWE-620, “Unverified Password Change”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
How serious is CWE-620?
It can affect access control, with impacts such as bypass protection mechanism, gain privileges or assume identity. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-620?
When prompting for a password change, force the user to provide the original password in addition to the new password. Do not use “forgotten password” functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the.
Can Codefreex check my site for CWE-620?
Yes. A senior engineer reviews your site, store or app for CWE-620 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-620 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.