Security readout for executives and security teams
Plain-English summary
CVE-2011-5314 is a Redaxscript 0.3.2 information disclosure issue. A direct web request to a template file can trigger an error message that reveals the server’s full filesystem path. This is not reported as code execution, but it can expose internal layout details useful for follow-on attacks.
Executive priority
Treat this as a low-priority legacy exposure unless Redaxscript 0.3.2 is internet-facing. Fix during routine hardening, but escalate if path disclosure appears on a public production site.
Technical view
The CVE identifies templates/default/index.php in Redaxscript 0.3.2 as directly requestable in a way that discloses the full path through an error message. The public bundle provides no CVSS score, CWE, patch version, or confirmed exploit activity.
Likely exposure
Exposure is limited to sites still running Redaxscript 0.3.2 with the affected template reachable from the public web and error details visible to remote users.
Exploitation context
The CVE describes remote information disclosure through a direct request. It is not listed in KEV, and the provided sources do not state active exploitation or public weaponization.
Researcher notes
Evidence is sparse: the bundle contains the CVE description and HTBridge advisory reference, but no CVSS, CWE, patch details, or exploit confirmation. Avoid expanding scope beyond Redaxscript 0.3.2 without additional vendor evidence.
Mitigation direction
- Inventory public Redaxscript sites and identify any running version 0.3.2.
- Check Redaxscript and HTBridge advisory guidance for version-specific remediation.
- Ensure production PHP error details are not displayed to remote users.
- Restrict direct access to template PHP files where vendor-supported.
Validation and detection
- Confirm whether Redaxscript 0.3.2 is present in production or legacy environments.
- Check whether templates/default/index.php is reachable from unauthenticated web clients.
- Review HTTP responses for full filesystem paths in error output.
- Verify error handling behavior after any vendor-guided remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2011-5314 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.htbridge.com/advisory/HTB22804CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.