WordPress 3.4.2 - Session Cookie Invalidation

wordpress Updated 02 Oct 2025

Summary

27/12/2012
N/A
No i
Unrated
Not published

CVE-2012-5868: WordPress 3.4.2 does not invalidate a wordpress_sec session cookie upon an administrator's logout action, which makes it easier for remote attackers to discover valid session identifiers via a brute-force attack, or modi... Affects wordpress versions 5.7.1+dfsg1-2 – 6.8.1+dfsg1-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

WordPress is a popular content management system (CMS) used for creating websites and blogs. It provides a user-friendly interface for managing website content, themes, and plugins. WordPress 3.4.2 is a specific version of WordPress that is vulnerable to a session cookie invalidation issue.

Vulnerability Detail

The vulnerability in WordPress 3.4.2 allows an attacker to discover valid session identifiers through a brute-force attack or modify data through a replay attack. When an administrator logs out, the wordpress_sec session cookie is not invalidated, making it possible for an attacker to use the session identifier to gain unauthorized access or manipulate data on the website.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. Upgrading to a patched version of WordPress is the recommended solution.

Conclusion

WordPress 3.4.2 is vulnerable to a session cookie invalidation issue, which can lead to unauthorized access or data manipulation on a website. It is crucial to upgrade to a patched version of WordPress to mitigate this vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for wordpress →

Share this vulnerability

FAQ

This vulnerability allows an attacker to gain unauthorized access to a WordPress website or manipulate data on the website.

Yes, this vulnerability can be exploited remotely by an attacker.

There may be known exploits for this vulnerability, so it is important to upgrade to a patched version of WordPress as soon as possible.

No, only WordPress 3.4.2 is known to be affected by this vulnerability.

Yes, upgrading to a newer version of WordPress that includes a patch for this vulnerability will fix the issue.

Related vulnerabilities

Recent vulnerabilities recorded for wordpress.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback