LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25065: WordPress WP Tabs Plugin <= 2.1.14 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in ShapedPlugin WP Tabs – Responsive Tabs Plugin for WordPress plugin <= 2.1.14 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WP Tabs WordPress plugin through version 2.1.14. A CSRF flaw could let an attacker trick a logged-in user into causing limited unauthorized changes or data exposure. It is not listed in CISA KEV, and the supplied sources do not show active exploitation.

Executive priority

Handle this as a routine but real WordPress plugin remediation item. It is medium severity with no cited active exploitation, but public disclosure and low attack complexity justify inventory, version validation, and timely update or removal.

Technical view

CVE-2023-25065 is a CWE-352 Cross-Site Request Forgery issue in ShapedPlugin WP Tabs – Responsive Tabs Plugin for WordPress, slug wp-expand-tabs-free, reported for versions <= 2.1.14. CVSS 3.1 is 5.4 with network attack vector, low complexity, no privileges required, required user interaction, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites that have the ShapedPlugin WP Tabs plugin installed at version 2.1.14 or earlier. Sites without this plugin, or with a version confirmed unaffected by vendor guidance, are not indicated as exposed by the provided bundle.

Exploitation context

The provided sources do not cite active exploitation, and the CVE is not marked KEV. Exploitation requires user interaction, consistent with CSRF risk against an authenticated browser session. The bundle does not identify the exact affected action or resulting business operation.

Researcher notes

The source bundle confirms the vulnerability class, affected plugin, version boundary, CVSS vector, and Patchstack reference. It does not provide the vulnerable endpoint, nonce behavior, affected administrative action, proof of exploitation, or named fixed version, so validation should avoid assuming those details.

Mitigation direction

  • Identify WordPress sites using ShapedPlugin WP Tabs or wp-expand-tabs-free.
  • Check vendor and Patchstack guidance for a confirmed fixed version.
  • Upgrade to a supported fixed release when confirmed by official guidance.
  • Disable or remove the plugin if no safe version is confirmed.
  • Limit privileged WordPress sessions until remediation is complete.

Validation and detection

  • Check each WordPress instance for plugin slug wp-expand-tabs-free.
  • Record installed WP Tabs versions and flag 2.1.14 or earlier.
  • Confirm whether vendor guidance identifies a fixed release after 2.1.14.
  • Review administrative history for unexpected WP Tabs changes.
  • Retest plugin functionality after update, disablement, or removal.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25065 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-25065Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ShapedPluginWP Tabs – Responsive Tabs Plugin for WordPresswp-expand-tabs-free, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.