GeniXCMS Cross-site Scripting (XSS) Vulnerability in genix/cms

genix/cms Updated 02 Oct 2025

Summary

17/05/2022
No i
Moderate
6.1

CVE-2017-14761: GeniXCMS Cross-site Scripting (XSS) vulnerability via id parameter. Affects genix/cms versions 1.1.4. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

GeniXCMS is a content management system that allows users to create and manage websites. It provides various features such as user management, page creation, and menu customization. The vulnerability in the genix/cms package allows for cross-site scripting (XSS) attacks via the id parameter in the menus.control.php file. This vulnerability can potentially lead to unauthorized access, data theft, and the execution of malicious code.

Vulnerability Detail

The GeniXCMS 1.1.4 version is affected by a cross-site scripting (XSS) vulnerability. The menus.control.php file does not properly sanitize user input in the id parameter, allowing an attacker to inject malicious scripts into the application. This can lead to the execution of arbitrary code in the context of the affected user's browser, potentially compromising sensitive information or performing unauthorized actions. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can manually sanitize the id parameter in the menus.control.php file to prevent the execution of malicious scripts. This can be done by using appropriate input validation and sanitization techniques, such as HTML entity encoding or using a secure framework that automatically handles input sanitization.

Conclusion

The GeniXCMS package is vulnerable to a cross-site scripting (XSS) attack via the id parameter in the menus.control.php file. This vulnerability can lead to unauthorized access, data theft, and the execution of malicious code. It is crucial to update the package to the latest version that includes a fix for this vulnerability. Additionally, users can apply temporary workarounds and utilize tools like Vulert Playground to check if their application is affected. For further support, contact DevNack.com.

See every vulnerability recorded for genix/cms →

Share this vulnerability

FAQ

This vulnerability allows an attacker to inject and execute arbitrary scripts in the context of the affected user's browser. It can lead to unauthorized access, data theft, and the execution of malicious code.

At the time of this advisory, there is no known public exploit for this vulnerability. However, it is important to apply the necessary security updates to mitigate the risk.

No, only GeniXCMS version 1.1.4 is affected by this vulnerability. It is recommended to update to the latest version to ensure the security of your application.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your composer.lock file to the playground, and it will analyze and alert you if the vulnerability is present.

For further support and assistance with vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.

Related vulnerabilities

Recent vulnerabilities recorded for genix/cms.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback