discuz forum personal space custom CSS style

Tips: When you see this prompt, it means that the current article has been migrated from the original emlog blog system. The publication time of the article is too long, and the formatting and content may not be complete. Please understand.

Custom CSS Styles for Discuz Forum Personal Space

Date: 2020-3-24 Ajue Code Fiddle: 1577 times Comments: 4

A few days ago, I had nothing to do, so I looked for vulnerabilities in the Discuz forum and actually found one. I wrote a software for it and then wrote an article about it.
The following is the cause of the incident:

This vulnerability does not pose a great threat to the website. It only allows customization of the CSS style of personal space, and does not pose a threat to website data, so please rest assured.

The software allows customization of the appearance of Discuz personal space, enriching and beautifying personal space, making it no longer monotonous.

Tested Discuz version X3.4, other versions self-tested.
Only tested on the Global Host Communication Forum (Webmaster, please spare me) , theoretically applicable to other versions of Discuz.
Not available for forums without personal space.
It is not recommended to use too much custom CSS, and it is recommended to compress it into one line to avoid failure.
Under normal circumstances, the protocol header does not need to be modified. The text box is mainly for easy expansion.
If you are operating on the loc forum, it will automatically listen and add Ajue Sauce as a friend [#manual funny + dog head to save life]

This software only makes local requests and does not upload any data to the server.
The software is packed, and antivirus software may report false positives, so please feel free to use it.

Get Cookie

Open the developer tools (F12) in the browser, go to the target website, on any page under the login status, switch to the Network tab in the developer tools, refresh the page (F5), find and click on the Headers column of the request data for the current domain name, and locate the cookie in the Request Headers. I know you probably don't understand what I'm saying, so I made a picture specifically.

The second method is simpler and faster, but this method is only applicable if you know which cookie you want. As shown in the figure below.

The developer tools in the first method have also been used in earlier blog posts, but they did not explain how to get the cookie. I still recommend the first method. After all, you can never have too many cookies, but it won't work if you have too few.

Disclaimer