#3396 closed defect (bug) (fixed)
Plugin version, etc. not sanitized like description is
| Reported by: | Viper007Bond | Owned by: | markjaquith |
|---|---|---|---|
| Priority: | lowest | Milestone: | 2.1 |
| Component: | Administration | Version: | 2.1 |
| Severity: | minor | Keywords: | has-patch |
| Cc: | Focuses: |
Description
We sanitize plugin descriptions with kses, so why not the version and such?
Try this in a plugin for example:
Version: 1.0 <script type="text/javascript">alert('I haxz0red your PC!');</script>
Now of course plugin authors could just put bad JS into the plugin itself, so this isn't really a security ticket, more a "let's-do-the-same-thing-to-all-fields" ticket (either sanitize them all or none).
Attachments (1)
Change History (7)
#5
@
20 years ago
Minor nitpicky note:
In the future, when using whitespace to align blocks of similar assignments (like the row of KSES calls), use spaces instead of tabs to make them line up. Many text editors can set tabs to be varying sizes, so they won't line up unless someone is using the same size tabs as you.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Agreed re: "all or nothing"
I'd go with "all," if only to stave off the inevitable "WordPress Security Bulletin: plugins can p0wn your WordPress!"
Patch it up!