Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

WP Plugin Info Card Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with WP Plugin Info Card, published between 2015 and 2026.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

4Total records
0Critical
0High
4Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2015-03-04First disclosure
2026-02-17Latest disclosure
3 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
201511 records
202522 records
202611 records

Severity Breakdown

SeverityRecordsShare
Medium4100%

Vulnerability-Type Breakdown

Cross-Site Scripting

3 records75%

First: 2015. Latest: 2025.

CSRF

1 record25%

First: 2026. Latest: 2026.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 6.3.0
  • 5.4.0
  • 5.3.1
  • 2.3.7

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-6.2.0WP Plugin Info Card <= 6.2.0 - Cross-Site Request Forgery to Arbitrary Custom Plugin Entry CreationFebruary 17, 20266.3.0Medium
*-5.3.1WP Plugin Info Card <= 5.3.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via containerid ParameterJune 2, 20255.4.0Medium
*-5.3.0WP Plugin Info Card <= 5.3.0 - Authenticated (Contributor+) Stored Cross-Site ScriptingApril 1, 20255.3.1Medium
[*, 2.3.7)WP Plugin Info Card < 2.3.7 - Cross-Site ScriptingMarch 4, 20152.3.7Medium

Selected source records

Latest Records

MediumCVE-2026-2023

WP Plugin Info Card <= 6.2.0 - Cross-Site Request Forgery to Arbitrary Custom Plugin Entry Creation

Published: February 17, 2026

Affected versions
*-6.2.0
Patched versions
6.3.0
Original Wordfence record
MediumCVE-2025-5116

WP Plugin Info Card <= 5.3.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via containerid Parameter

Published: June 2, 2025

Affected versions
*-5.3.1
Patched versions
5.4.0
Original Wordfence record
MediumCVE-2025-31835

WP Plugin Info Card <= 5.3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: April 1, 2025

Affected versions
*-5.3.0
Patched versions
5.3.1
Original Wordfence record
Medium

WP Plugin Info Card < 2.3.7 - Cross-Site Scripting

Published: March 4, 2015

Affected versions
[*, 2.3.7)
Patched versions
2.3.7
Original Wordfence record

Highest-Severity Records

MediumCVE-2025-31835

WP Plugin Info Card <= 5.3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: April 1, 2025

Affected versions
*-5.3.0
Patched versions
5.3.1
Original Wordfence record
MediumCVE-2025-5116

WP Plugin Info Card <= 5.3.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via containerid Parameter

Published: June 2, 2025

Affected versions
*-5.3.1
Patched versions
5.4.0
Original Wordfence record
Medium

WP Plugin Info Card < 2.3.7 - Cross-Site Scripting

Published: March 4, 2015

Affected versions
[*, 2.3.7)
Patched versions
2.3.7
Original Wordfence record
MediumCVE-2026-2023

WP Plugin Info Card <= 6.2.0 - Cross-Site Request Forgery to Arbitrary Custom Plugin Entry Creation

Published: February 17, 2026

Affected versions
*-6.2.0
Patched versions
6.3.0
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory