Back to list

Information Disclosure via X-Powered-CMS Header

Description

The 'X-Powered-CMS' header reveals which content management system (CMS) powers the application, potentially including version or branding details. By exposing this information, attackers can focus their reconnaissance on known vulnerabilities, default configurations, and unpatched extensions associated with that CMS. They may also conduct more convincing social engineering attacks by referencing the specific CMS in phishing or support scams. Ultimately, disclosing the CMS technology broadens the attack surface by making it easier for malicious actors to launch exploits tailored to that platform’s known weaknesses.

Remediation

Remove or mask the 'X-Powered-CMS' header in your server or CMS configuration so that external clients are not informed of your platform details. Ensure that any reverse proxies, CDNs, or load balancers do not re-inject or preserve this header. Keep your CMS installation, themes, and plugins regularly patched to avoid well-known or zero-day exploits. Consider employing a Web Application Firewall (WAF) or intrusion detection system to detect malicious traffic targeting CMS-specific endpoints. Regularly audit your headers and server logs to ensure no environment information is inadvertently leaking through response headers.

References

https://owasp.org/www-community/attacks/Information_exposurehttps://developer.mozilla.org/en-US/docs/Web/HTTP/Headers

Severity

MEDIUM

Owasp

Code: A05:2021

Category: Security Misconfiguration

Classification

CWE-200
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

5.3

CVSS:4.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

5.3