User tests: Successful: Unsuccessful:
[4] revert and improve #32013 to use htmlspecialchars on user supplied placeholders and use non html entity for the bullet to overcome the entity being destroyed by htmlspecialchars
Look at Joomla Global Configuration Database Password field - ensure placeholders are • and not asterisks or badly formatted
Potential XSS on any non-core use of this field with a user supplied $hint and $lock set to no.
In line with all other user supplied placeholders, htmlspecialchars is applied to prevent XSS injections.
None.
// @brianteeman
| Status | New | ⇒ | Pending |
| Category | ⇒ | Layout |
| Labels |
Added:
?
|
||
Merged back 4.0-dev and fixed cs, and reverted back to bootstrap 5 version. Ready to test again.
I have tested this item
I have tested this item
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-02-08 08:42:46 |
| Closed_By | ⇒ | infograf768 | |
| Labels |
Added:
?
|
||
Tks
I have tested this item✅ successfully on 2fc4784
I see the bullets in the password field and the two changes to the layout file.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32044.