From f9f16a91a608f694efa513675d5ebece6509ad97 Mon Sep 17 00:00:00 2001
From: wstgbot <62450690+wstgbot@users.noreply.github.com>
Date: Tue, 27 Feb 2024 21:38:53 +0000
Subject: [PATCH] Publish Latest 2024-02-27

Updates based on OWASP/wstg@a6c4017
---
 .../03-Testing_for_Privilege_Escalation.md                      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/latest/4-Web_Application_Security_Testing/05-Authorization_Testing/03-Testing_for_Privilege_Escalation.md b/latest/4-Web_Application_Security_Testing/05-Authorization_Testing/03-Testing_for_Privilege_Escalation.md
index 72a255e..648fbef 100644
--- a/latest/4-Web_Application_Security_Testing/05-Authorization_Testing/03-Testing_for_Privilege_Escalation.md
+++ b/latest/4-Web_Application_Security_Testing/05-Authorization_Testing/03-Testing_for_Privilege_Escalation.md
@@ -195,7 +195,7 @@ startswith(), endswith(), contains(), indexOf()
 
 ### Weak SessionID
 
-Weak Session ID has algorithm may be vulnerable to brute Force attack. For example, one site is using `MD5(Password + UserID)` as sessionID. Then, testers may guess or generate the sessionID for other users.
+Weak Session ID has algorithm may be vulnerable to brute force attack. For example, one site is using `MD5(Password + UserID)` as sessionID. Then, testers may guess or generate the sessionID for other users.
 
 ## References