LiveActive security incident?Get immediate response
CVE Record

CVE-2025-23898: WordPress Apply with LinkedIn buttons plugin <= 2.3 - CSRF to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in ivobrett Apply with LinkedIn buttons apply-with-linkedin-buttons allows Stored XSS.This issue affects Apply with LinkedIn buttons: from n/a through <= 2.3.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

WordPress sites using Apply with LinkedIn buttons version 2.3 or earlier may be exposed to a CSRF issue that can lead to stored cross-site scripting. In business terms, a tricked administrator could unintentionally save malicious content that later runs in browsers. The source bundle does not identify a patched version.

Executive priority

Treat this as high priority for WordPress environments using the plugin. It is not confirmed as actively exploited in the provided sources, but stored XSS can create reputational, data exposure, and site integrity risk.

Technical view

CVE-2025-23898 is a CWE-352 CSRF vulnerability in the apply-with-linkedin-buttons WordPress plugin through version 2.3, reported as CSRF to Stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges, required user interaction, and changed scope.

Likely exposure

Exposure is likely limited to WordPress installations with the Apply with LinkedIn buttons plugin installed at version 2.3 or earlier. The bundle does not provide CPEs or installation prevalence.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The attack requires user interaction, consistent with CSRF, and could result in stored XSS if an authorized user is tricked.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. The bundle does not include vulnerable endpoint details, proof of concept, exploit telemetry, patch version, or vendor advisory text. Avoid assuming broader product impact beyond Apply with LinkedIn buttons through 2.3.

Mitigation direction

  • Inventory WordPress sites for the Apply with LinkedIn buttons plugin.
  • Prioritize sites running version 2.3 or earlier.
  • Check vendor, WordPress, and Patchstack guidance for an update or official mitigation.
  • Disable or remove the plugin where it is not business-critical.
  • Review affected sites for unexpected stored content or configuration changes.

Validation and detection

  • Confirm whether apply-with-linkedin-buttons is installed on each WordPress site.
  • Record the installed plugin version and flag version 2.3 or earlier.
  • Review administrative content and plugin settings for suspicious injected HTML or scripts.
  • Check security monitoring for unusual administrator-session activity around plugin configuration changes.
  • Verify any remediation against vendor or Patchstack guidance before closure.
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-2025-23898 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-23898Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ivobrettApply with LinkedIn buttonsapply-with-linkedin-buttons, 0unaffected
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.