CVE-2026-1468
Received Received - Intake
Cross-Site Request Forgery in QuickCMS 6.8 Allows Privilege Abuse

Publication date: 2026-03-06

Last updated on: 2026-03-06

Assigner: CERT.PL

Description
QuickCMS is vulnerable to Cross-Site Request Forgery across multiple endpoints. An attacker can craft special website, which when visited by the victim, will automatically send a POST request with victim's privileges. This software does not implement any protection against this type of attack. All forms available in this software are potentially vulnerable. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.8 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-06
Last Modified
2026-03-06
Generated
2026-05-07
AI Q&A
2026-03-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
opensolution quickcms to 6.8 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': "CVE-2026-1468 is a Cross-Site Request Forgery (CSRF) vulnerability found in QuickCMS version 6.8. This vulnerability allows an attacker to create a malicious webpage that, when visited by an administrator or user with privileges, automatically sends a POST request to the QuickCMS system. This request can perform actions such as creating a product with attacker-defined content without the victim's authorization."}, {'type': 'paragraph', 'content': 'The software does not implement any protection against CSRF attacks, making all forms within QuickCMS potentially vulnerable.'}] [1]


How can this vulnerability impact me? :

This vulnerability can allow attackers to perform unauthorized actions on behalf of authenticated users, such as administrators, without their consent. For example, an attacker can create or modify content within the QuickCMS system by tricking the victim into visiting a malicious webpage.

Such unauthorized actions can lead to data manipulation, content injection, or other malicious changes within the CMS, potentially compromising the integrity and trustworthiness of the website managed by QuickCMS.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'Detection of this Cross-Site Request Forgery (CSRF) vulnerability involves monitoring for unauthorized POST requests sent to QuickCMS endpoints, especially those that create or modify content without proper authorization.'}, {'type': 'paragraph', 'content': 'Since QuickCMS lacks any CSRF protection, one way to detect exploitation attempts is to analyze web server logs for suspicious POST requests originating from external or unexpected sources.'}, {'type': 'paragraph', 'content': 'Commands to assist detection might include using tools like curl or wget to simulate POST requests and observe responses, or using network monitoring tools such as tcpdump or Wireshark to capture and analyze HTTP traffic.'}, {'type': 'list_item', 'content': "Use curl to simulate a POST request to QuickCMS endpoints: curl -X POST -d 'param=value' https://your-quickcms-site/path"}, {'type': 'list_item', 'content': "Check web server logs for unexpected POST requests: grep 'POST' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "Capture HTTP traffic to detect suspicious POST requests: sudo tcpdump -i eth0 -A 'tcp port 80 or tcp port 443'"}] [1]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing CSRF protection mechanisms such as adding CSRF tokens to all forms and validating them on the server side.

If modifying the application is not immediately possible, restrict access to the QuickCMS administrative interface by IP address or VPN to limit exposure.

Additionally, educate users and administrators to avoid clicking on suspicious links or visiting untrusted websites while logged into QuickCMS.

Regularly monitor logs for suspicious activity and consider applying web application firewall (WAF) rules to block unauthorized POST requests.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart