You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Paper 1.21.8 - Bug: Click and Hover tags inside [item] allow execution of dangerous commands #3278
Rename an item using an anvil and add clickable or hover tags inside its name, e.g. <click:run_command:"/suicide">.
When a player clicks on the item name in chat, the command executes immediately, causing harm (like suicide).
Similarly, clickable admin names can grant OP if clicked accidentally.
What is your expected behavior and what happened instead? How can we reproduce the issue?
Expected behavior: ChatControl should block or sanitize hover and click tags inside [item] placeholders, disallowing commands or any dangerous interactions triggered by item names. Actual behavior: Click and hover tags inside item names work and can trigger commands, which may harm players or give admins unintended permissions.
You have removed the settings, but they are not by default and that chat does not work the same way. My chat is broken, so I had to roll it back to the old version.
@BAD7777 which settings were removed which you were using?
Improve | Simplified plugin settings by removing least used options to improve usability.
List of removed options and their default state:
Ignore_Autojoin_If_Left; Ignore_Death_Messages; Support_Variables_In_Variables; Support_Full_PlaceholderAPI_Syntax; Support_Relational_Placeholders; Upgrade_Hex_To_Mini_In_Variables and Make_Chat_Links_Clickable are now always true
Play_Sound_If_No_Message is now always false
@BAD7777 are you saying you were using ALL of the removed options? They are still enabled and working (i.e. the Performance keys) we just deleted they from settings.yml
@BAD7777 are you saying you were using ALL of the removed options? They are still enabled and working (i.e. the Performance keys) we just deleted they from settings.yml
I updated to the latest version, and it caused complete chaos in the chat. Then I reverted to the old version, and everything worked fine again.
What's shown in the screenshot is likely the default values, but in any case, after reverting to the version one step lower, everything works perfectly.
Activity
devpedrobarbosa commentedon Aug 12, 2025
@BAD7777
Thanks for sharing that.
We'll be going through this ASAP.
devpedrobarbosa commentedon Aug 14, 2025
@BAD7777
As an imediate fix, just fill
Suggest_Commandinsidevariables/item.ymlwith anything, even a single space (Sugges_Command: ' ').We're working on a proper patch and will release it ASAP.
devpedrobarbosa commentedon Aug 14, 2025
@BAD7777
I've published an update and it comes with a patch for this.
Will probably improve it, though.
devpedrobarbosa commentedon Aug 14, 2025
Please let me know if it works on your end :)
BAD7777 commentedon Aug 14, 2025
[item]
BAD7777 commentedon Aug 14, 2025
You have removed the settings, but they are not by default and that chat does not work the same way. My chat is broken, so I had to roll it back to the old version.
kangarko commentedon Aug 14, 2025
@BAD7777 which settings were removed which you were using?
BAD7777 commentedon Aug 14, 2025
Improve | Simplified plugin settings by removing least used options to improve usability.
List of removed options and their default state:
Ignore_Autojoin_If_Left; Ignore_Death_Messages; Support_Variables_In_Variables; Support_Full_PlaceholderAPI_Syntax; Support_Relational_Placeholders; Upgrade_Hex_To_Mini_In_Variables and Make_Chat_Links_Clickable are now always true
Play_Sound_If_No_Message is now always false
BAD7777 commentedon Aug 14, 2025
devpedrobarbosa commentedon Aug 14, 2025
They were removed but were supposed to be working. Will take a look at that ASAP.
BAD7777 commentedon Aug 14, 2025
Thank you very much, I'll be waiting. Regarding [item], it still works click.
kangarko commentedon Aug 14, 2025
@BAD7777 are you saying you were using ALL of the removed options? They are still enabled and working (i.e. the Performance keys) we just deleted they from settings.yml
BAD7777 commentedon Aug 14, 2025
I updated to the latest version, and it caused complete chaos in the chat. Then I reverted to the old version, and everything worked fine again.
What's shown in the screenshot is likely the default values, but in any case, after reverting to the version one step lower, everything works perfectly.
2 remaining items
BAD7777 commentedon Aug 15, 2025
&#D3D3D3 doesnt work <#D3D3D3> work
devpedrobarbosa commentedon Aug 15, 2025
Is this the only issue had using 11.4.8?
If not could you give me examples of what's not working?
BAD7777 commentedon Aug 15, 2025
At the moment, I only noticed this issue and that's it. [item] Everything works like that, and the button is pressed.
devpedrobarbosa commentedon Aug 15, 2025
So you're using hex format
𞉀inside your format like this?If so, did it use to work on previous versions? This is only supposed to work in variables.
BAD7777 commentedon Aug 15, 2025
yes. im using luckperms prefix and suffix
devpedrobarbosa commentedon Aug 15, 2025
So the
𞉀is coming from LuckPerms prefix like this?BAD7777 commentedon Aug 15, 2025
devpedrobarbosa commentedon Aug 15, 2025
It's working fine for me.
Could you please clarify where this legacy hex codes are coming from?
Also, if you're able to, please test this jar (exact one I'm using) to see if there was some mismatch when publishing.
ChatControl-dev.zip
BAD7777 commentedon Aug 15, 2025
Everything is working. Thanks
BAD7777 commentedon Aug 15, 2025
All that remains now is to fix [item]
devpedrobarbosa commentedon Aug 15, 2025
@BAD7777
Just to clarify:
BAD7777 commentedon Aug 15, 2025
devpedrobarbosa commentedon Aug 16, 2025
@BAD7777
Thanks for the update. I fixed it. Will be released ASAP.
BAD7777 commentedon Aug 16, 2025
goods, thanks!
devpedrobarbosa commentedon Aug 16, 2025
Thanks for sharing that. I removed the debug and updated the resource.