Security readout for executives and security teams
Plain-English summary
This flaw affects the WordPress Media File Renamer plugin through version 5.1.9. A successful CSRF attack could cause a logged-in user’s browser to change uploaded media titles, filenames, or locking state. That can disrupt content integrity and site operations, but the sources do not indicate data theft or server compromise.
Executive priority
Treat this as a moderate-priority WordPress integrity issue. It is not presented as actively exploited or highly destructive, but affected public sites should be inventoried and remediated because unauthorized filename or media-state changes can break pages and damage trust.
Technical view
CVE-2021-36850 is a CWE-352 CSRF issue in Meow Apps Media File Renamer. The affected parameters are post_title, filename, and lock. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites using Media File Renamer – Auto & Manual Rename version 5.1.9 or earlier. Sites with active media workflows or privileged users managing uploaded files have more practical risk because the impact is unauthorized media metadata, filename, or lock-state changes.
Exploitation context
The provided sources and KEV status do not support active exploitation. The CVSS vector indicates user interaction is required. As a CSRF issue, practical abuse likely depends on a logged-in WordPress user being induced to trigger an unwanted request, but source details are limited.
Researcher notes
Evidence is concise: affected versions are listed as <= 5.1.9, impacted parameters are named, and the stated impact is media title, filename, and lock-state modification. No exploit details, patch version, or in-the-wild exploitation evidence are provided in the bundle.
Mitigation direction
- Inventory WordPress sites for the Media File Renamer plugin and installed version.
- Check Meow Apps, WordPress.org, and Patchstack guidance for the fixed version.
- Update to a vendor-confirmed fixed release when identified.
- Disable or remove the plugin where a fixed release cannot be verified.
- Review media-management permissions for unnecessary privileged users.
Validation and detection
- Confirm no site runs Media File Renamer version 5.1.9 or earlier.
- Review WordPress plugin changelog and Patchstack entry for remediation status.
- Check recent media titles, filenames, and lock states for unexplained changes.
- Verify only trusted users can manage uploaded media.
- Document affected sites and remediation decisions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2021-36850 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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:N/I:L/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/media-file-renamer/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/media-file-renamer/wordpress-media-file-renamer-plugin-5-1-9-multiple-cross-site-request-forgery-csrf-vulnerabilitiesCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.