-
Notifications
You must be signed in to change notification settings - Fork 99
CSRF Vulnerabilities in TypesetterCMS (Version - 5.1) [CVE-2022-25523] #697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This vulnerability/CVE - https://www.exploit-db.com/exploits/44029 was for admins but my report is for user-level privileges. |
I tested Your above html - code (pushstate) with Edge (and newest Firefox) at one of my 5.2-sites .../User with result after klick at the button : Not found - The requested page does not exist. Please use the website navigation to reach the existing pages. Opera gives already before a long warning.
|
@gtbu This vulnerability is present in 5.1 versions and could be patched in 5.2 which is a good thing. |
Last release in August 2017. I think this CMS is dead. |
For what do You make such a comment ! ? There is a fork at github.com/gtbu which is php8-ready. |
That's correct, but only available as a beta. I know you are working on a PHP8-ready version, but this repository (from the origin maintainer) is outdated. I am sorry to say that, but that's a fact. I like Typesetter, its a lightweight, easy to use and fast CMS, but I only want to use releases (which are not in alpha or beta status). If the maintainer doesn't continuing the work and nobody adopted this project to proceed the engineering - the CMS is dead. This is what it looks like for me. Sorry. |
And unofficial releases are prone to supply chain attacks. ^^ |
The only known possibility was in the download of plugins and templates (has been fixed in the php8-version in common.php http://www.typesettercms.com' to https://www.typesettercms.com') for web-installation. |
I found this issue in an official version - TypesetterCMS - =5.1 Adding this vulnerability here is a must as an open-source contribution so if someone tries to use this version should be aware of this beforehand. I found this vulnerability on https://www.typesettercms.com/User on March 24, 2022. |
Sorry : You are riding on a dead horse : We use Typesetter 5.2+. Of course it would be possible to prevent compromised packages by adding hashes etc.. |
Good for you. The official release yet on the OFFICIAL Typesetter releases page is 5.1 - Kindly visit https://github.com/Typesetter/Typesetter/releases This issue was created for those who do follow the officially released versions *which is 5.1 as the latest and is eventually vulnerable to Cross-site request forgery. |
Your fork is good to go but anyone who is using the typesetter repo for this and referring to https://github.com/Typesetter/Typesetter/releases should be aware of this stuff. There is nothing wrong with sharing vulnerabilities. There is ? |
Please change the issue name to point its version dependency |
Thx |
TypesetterCMS v5.1 was discovered to contain a Cross-Site Request
Forgery (CSRF) which is exploited via a crafted POST request.
Vulnerability Type
Cross-Site Request Forgery (CSRF)
Vendor of Product
TypesetterCMS
Affected Product Code Base
TypesetterCMS - =5.1 are effected
Affected Component
All the POST requests
Attack Type
Remote
Impact Escalation of Privileges
true
Attack Vector
Discoverers
Danish Tariq
Ali Hassan Ghori
Reference
http://typesettercms.com
https://www.typesettercms.com/User
The text was updated successfully, but these errors were encountered: