Security readout for executives and security teams
Plain-English summary
CVE-2025-49869 affects the WordPress Eventin plugin. A logged-in attacker may be able to abuse unsafe deserialization to inject PHP objects, with potential impact to site data, integrity, and availability. The source bundle rates it high severity with CVSS 8.8.
Executive priority
Treat as high priority for WordPress properties using Eventin, especially public sites with user registration or many contributor-level accounts. Confirm exposure quickly, then apply vendor guidance or reduce plugin availability until remediated.
Technical view
The vulnerability is CWE-502, deserialization of untrusted data, in Arraytics Eventin wp-event-solution through version 4.0.31. CVSS indicates network access, low attack complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running the Eventin plugin wp-event-solution at version 4.0.31 or earlier. CVSS requires low privileges, so sites with untrusted or broadly issued accounts deserve extra attention.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. Patchstack has a vulnerability database entry, but the provided evidence does not include exploit maturity, observed attacks, or detailed attack path.
Researcher notes
Evidence is sufficient for vulnerability classification and affected range, but incomplete on patched version, exploit details, and real-world exploitation. Avoid assuming unauthenticated exploitation because the CVSS vector specifies PR:L.
Mitigation direction
- Inventory WordPress sites for Eventin wp-event-solution installations.
- Identify any installed Eventin version at 4.0.31 or earlier.
- Check Arraytics and Patchstack guidance for a fixed release or vendor mitigation.
- Update once a vendor-confirmed safe version is available.
- Disable or remove the plugin temporarily where business impact allows.
- Review account access, especially low-privilege users on affected sites.
Validation and detection
- Confirm plugin slug and version from WordPress administration or asset inventory.
- Compare installed versions against the affected range through 4.0.31.
- Review vendor and Patchstack advisories for current remediation status.
- Check whether affected sites allow untrusted low-privilege accounts.
- Review relevant WordPress logs for unusual authenticated activity.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-2025-49869 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
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:L/UI:N/S:U/C:H/I:H/A:H2.85.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/wp-event-solution/vulnerability/wordpress-eventin-plugin-4-0-31-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.