Home / Core Health / Remove version-disclosing files (readme.html, CHANGELOG.txt)
Exposed Files · Scan Check Guide

Remove version-disclosing files (readme.html, CHANGELOG.txt)

20 min Impact: medium Effort: low ✓ Scan-verified — no manual checkbox

Many CMSs and frameworks expose their exact version number in page source, meta tags, or readme files (a WordPress /readme.html, a generator meta tag) — giving attackers a direct lookup for known vulnerabilities specific to that version.

Default CMS readme and changelog files hand attackers your exact software version — letting them look up known vulnerabilities for that specific release instead of guessing blindly.

The full picture

Version-disclosing files like readme.html and CHANGELOG.txt, often included by default with common content management systems and software packages, reveal your exact software version to anyone who checks these standard, predictable file locations — this represents the same reconnaissance-enabling risk discussed regarding server version headers, applied to a different, file-based disclosure point.

The genuine risk this creates mirrors the broader version-disclosure principle discussed elsewhere — knowing your exact software version allows an attacker to check that specific version against known, documented vulnerabilities, potentially identifying an exploitable weakness without any active probing beyond simply requesting these standard, predictable file paths.

These files are commonly included by default in software distribution packages and frequently never removed during deployment, meaning many sites unknowingly expose this information not through any deliberate choice but simply through never having addressed default files that ship with their underlying software.

Removing or restricting access to these specific files represents genuinely low-effort remediation — these files typically serve no functional purpose once your site is actually deployed and running, making their removal a safe, straightforward action that closes off this particular reconnaissance opportunity with essentially no functional tradeoff.

How to fix it

  1. 1
    Check common disclosure points
    View your page source for a <meta name="generator"> tag, and check for a /readme.html or /CHANGELOG file at your root.
  2. 2
    Remove or block what you find
    Most CMSs have a plugin or one-line config change to strip the generator meta tag; delete or block direct access to readme/changelog files.
  3. 3
    Keep the actual software updated regardless
    Hiding the version number is a minor speed bump — staying current on security patches is what actually matters.

Common mistakes

How you'll know it's done

No generator meta tag or readme/changelog file reveals your exact CMS version publicly.

H.I.V.E. checks this automatically

Fix it, then re-scan — the check confirms itself. No manual checkbox, the scan is the truth.

Run this check in H.I.V.E. →