CWE-1473: Improper Expiration of Cached Data | Codefreex Skip to content

Security weakness

CWE-1473 Improper Expiration of Cached Data

A class-level weakness that can lead to data, pages or code changed and accounts and admin areas exposed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-1473?

Improper Expiration of Cached Data: The product uses or supports data in a cache, but it does not properly specify an expiration with a date, time, or time period that is sufficient for the intended security policy of the product or its adminstrators.

Business impact

What CWE-1473 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Gain Privileges or Assume Identity
  • Bypass Protection Mechanism
  • Unexpected State

Access Control

Accounts and admin areas exposed

Logins and permission checks can be bypassed, putting admin and customer accounts at risk.

  • Gain Privileges or Assume Identity
  • Bypass Protection Mechanism
  • Unexpected State

Free security check

Is CWE-1473 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-1473

Improper Expiration of Cached Data

The product uses or supports data in a cache, but it does not properly specify an expiration with a date, time, or time period that is sufficient for the intended security policy of the product or its adminstrators.

Weakness ID
CWE-1473
Type
Class
Status
Incomplete
Introduced during
Implementation

Prevention

How to fix CWE-1473, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • For each type of cached data, determine the best lifetime that balances efficiency provided by the cache with the security implications of the data becoming too stale. Explicitly specify an expiration date or time period.

Detection and evidence

How CWE-1473 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

Real vulnerabilities it caused

  • [REF-1581]RESTful search engine caches DNS hostname lookups forever in order to prevent DNS spoofing attacks, but it will not be able to detect when the hostnames resolve to a different IP address.

How we fix it

From finding to fixed: how Codefreex closes CWE-1473

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-1473: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-1473?

CWE-1473, “Improper Expiration of Cached Data”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product uses or supports data in a cache, but it does not properly specify an expiration with a date, time, or time period that is sufficient for the intended security policy of the product or its adminstrators.

How serious is CWE-1473?

It can affect access control, integrity, other, with impacts such as gain privileges or assume identity, bypass protection mechanism, unexpected state. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-1473?

For each type of cached data, determine the best lifetime that balances efficiency provided by the cache with the security implications of the data becoming too stale. Explicitly specify an expiration date or time period.

Can Codefreex check my site for CWE-1473?

Yes. A senior engineer reviews your site, store or app for CWE-1473 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-1473 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.