PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-13170 Eventin CVE debrief

The Eventin WordPress plugin before 4.1.20 does not properly validate a template path setting before using it to include a local file, allowing users with editor-level access and above to include and execute arbitrary local PHP files. This vulnerability affects users with editor-level access and above, potentially allowing them to execute arbitrary PHP code. The plugin's failure to validate the template path setting could lead to unauthorized code execution.

Vendor
Eventin
Product
Eventin WordPress plugin
CVSS
HIGH 7.2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-10
Original CVE updated
2026-08-26
Advisory published
2026-08-10
Advisory updated
2026-08-26

Who should care

Users of the Eventin WordPress plugin, especially those with editor-level access, and security teams responsible for vulnerability management and monitoring, should be aware of this vulnerability and take necessary precautions to prevent exploitation. Affected operators and platforms should review their deployments and apply patches or mitigations as needed. Vulnerability management and security teams should prioritize patching and monitoring for suspicious activity related to the plugin. Additionally, defenders should verify plugin versions, user access controls, and monitor for suspicious activity to minimize potential impact. Compensating controls for exposed systems should be reviewed while remediation is scheduled and verified. Relevant monitoring, detection, and logs for exposed assets should be checked for extra review. Security teams should also consider the potential operational impact of this vulnerability and plan accordingly.

Technical summary

The Eventin WordPress plugin before 4.1.20 is vulnerable to a local file inclusion (LFI) attack due to improper validation of a template path setting. Users with editor-level access and above can exploit this vulnerability to include and execute arbitrary local PHP files, potentially leading to code execution.

Defensive priority

Patch and verify plugin version; restrict editor-level access; monitor for suspicious activity

Recommended defensive actions

  • Patch the Eventin WordPress plugin to version 4.1.20 or later
  • Restrict editor-level access to only necessary users
  • Monitor for suspicious activity related to the plugin
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The Eventin WordPress plugin before 4.1.20 does not properly validate a template path setting before using it to include a local file, allowing users with editor-level access and above to include and execute arbitrary local PHP files. Evidence is limited; verify plugin version and user access controls; monitor for suspicious activity. Additional verification tasks are needed to confirm affected scope and severity.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-13170 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-13170

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-13170 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-13170

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.