LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25411: WordPress Revision Manager TMC plugin <= 2.8.22 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in themastercut Revision Manager TMC revision-manager-tmc allows Cross Site Request Forgery.This issue affects Revision Manager TMC: from n/a through <= 2.8.22.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25411 is a medium-severity CSRF issue in the WordPress Revision Manager TMC plugin through version 2.8.22. A victim with appropriate WordPress access would need to be tricked into taking an action, such as visiting a crafted page. Expected impact is limited integrity change, not data theft or service outage based on the CVSS vector.

Executive priority

Treat this as a routine but real WordPress plugin remediation item. Prioritize sites where many users have publishing or administrative access. It is not currently documented as exploited in the provided sources, and the expected technical impact is limited to integrity.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in themastercut Revision Manager TMC, package revision-manager-tmc, affecting versions through 2.8.22. CVSS 3.1 is 4.3: network exploitable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites with Revision Manager TMC installed at version 2.8.22 or earlier. The provided affected-version metadata is inconsistent, listing versions through 2.8.22 but also an affected version value of 0, so confirm locally.

Exploitation context

The source bundle does not report active exploitation, and CISA KEV status is false. CSRF generally depends on enticing an authenticated user to interact with attacker-controlled content. No public exploit details are provided in the supplied sources.

Researcher notes

Evidence is sparse beyond the CVE description, CVSS vector, CWE, and Patchstack reference. The bundle does not provide vulnerable endpoints, proof of concept, fixed version, or exploit activity. Validate affected status carefully because the structured affected-version field conflicts with the narrative range.

Mitigation direction

  • Inventory WordPress sites for the revision-manager-tmc plugin.
  • Identify installations running Revision Manager TMC version 2.8.22 or earlier.
  • Check the vendor or Patchstack entry for fixed versions or official remediation.
  • Apply an official update if available and tested.
  • Limit administrator access and reinforce CSRF-aware operational practices.

Validation and detection

  • Confirm whether Revision Manager TMC is installed on each WordPress site.
  • Record the installed plugin version from trusted administrative sources.
  • Compare the version against the reported affected range through 2.8.22.
  • Review vendor or Patchstack guidance for status and remediation details.
  • Monitor logs for suspicious administrative changes, without assuming exploitation.
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-2026-25411 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-25411Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
themastercutRevision Manager TMCrevision-manager-tmc, 0unaffected
Weakness

CWE details

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