fix a typo with the use of CVE-2025-55102, it should be CVE-2025-55182 #20760
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jheysel-r7
approved these changes
Dec 9, 2025
Contributor
jheysel-r7
left a comment
jheysel-r7
left a comment
There was a problem hiding this comment.
LGTM 👍
Testing
➜ metasploit-framework git:(1a8e88c054) rg "55102"
➜ metasploit-framework git:(1a8e88c054) find . -name "*55102*"
➜ metasploit-framework git:(1a8e88c054)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a typo in several places for the CVE ID used in the recent react2shell exploit module from pull request #20747. The string
cve_2025_55102should becve_2025_55182(Note the 8 in the second last character).This commit renames the affected files and content in several places (Including
db/modules_metadata_base.json, which is ok to modify directly I assume?)