WordPress 0.72
WordPress 0.72
The WordPress 0.72 reached end of service life on Jan 3, 2004 — WordPress no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your WordPress 0.72 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- wordpress
- release
- 0.72
- product Label
- WordPress
- release Label
- 0.72
- codename
- lts
- latest Version
- 0.72
- release Date
- 2003-10-11
- maintained
- source Url
- https://endoflife.date/wordpress
Lifecycle Dates
- End of Service Life
- Jan 3, 2004
- Last OEM Support
- Jan 3, 2004
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for WordPress 0.72 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for WordPress 0.72?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for WordPress 0.72 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
WordPress 0.72 Support: Frequently Asked Questions
Is the WordPress 0.72 still supported?
WordPress ended support for the WordPress 0.72 on Jan 3, 2004 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the WordPress 0.72 end of service life (EOSL) date?
WordPress lists the end of service life for the WordPress 0.72 as Jan 3, 2004.
Can I keep using the WordPress 0.72 after its EOSL date?
Yes. EOSL means WordPress stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the WordPress 0.72 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting WordPress 0.72
1 published CVE affects the WordPress 0.72, including 1 rated critical or high severity. WordPress no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2011-4899 | HIGH | 7.5 | Jan 30, 2012 | wp-admin/setup-config.php in the installation component in WordPress 3.3.1 and earlier does not ensure that the specified MySQL database service is appropriate, which allows remote attackers to configure an arbitrary database via the dbhost and dbname parameters, and subsequently conduct static code injection and cross-site scripting (XSS) attacks via (1) an HTTP request or (2) a MySQL query. NOTE: the vendor disputes the significance of this issue; however, remote code execution makes the issu |