CVE-2025-5812
BaseFortify
Publication date: 2025-06-26
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the VG WORT METIS WordPress plugin is due to a missing capability check in the function gutenberg_save_post(). This allows authenticated users with Subscriber-level access or higher to modify certain post settings without proper authorization. Essentially, users who should have limited permissions can update limited post settings, which they normally should not be able to change.
How can this vulnerability impact me? :
This vulnerability can allow users with low-level access (Subscriber and above) to modify limited post settings, potentially leading to unauthorized changes in content or post metadata. While it does not allow full control or content deletion, it can impact the integrity of post data and may be exploited to alter tracking or identification settings managed by the plugin.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves unauthorized modification of post settings via the gutenberg_save_post() function in the VG WORT METIS WordPress plugin. Detection can focus on monitoring for unexpected changes to post metadata or settings by users with Subscriber-level access or higher. Since the vulnerability is in the plugin's backend PHP code, direct network detection commands are not provided. However, you can audit WordPress logs for post update actions by low-privilege users or use WordPress CLI commands to check plugin versions and post metadata changes. For example, use `wp plugin list` to verify the plugin version, and `wp post meta get <post_id> _metis_text_type` or `_metis_text_length` to check for suspicious metadata changes. Additionally, reviewing user roles and recent post edits via WordPress admin or logs can help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the VG WORT METIS plugin to a version later than 2.0.0 where the missing capability check on gutenberg_save_post() is fixed. If an update is not yet available, restrict Subscriber-level users from editing posts or disable the plugin temporarily. Additionally, review and tighten user permissions to prevent unauthorized post modifications. Monitoring and logging post changes by low-privilege users can also help detect exploitation attempts until a patch is applied. [1]