dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-7813

HIGH · 7.2 CVSS v3.1 Published 2025-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Events Calendar, Event Booking, Registrations and Event Tickets – Eventin plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.0.37 via the proxy_image function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Eventin WordPress plugin contains an SSRF vulnerability in its proxy_image function. Unauthenticated attackers can abuse this function to make arbitrary HTTP requests from the server, potentially accessing internal services, cloud metadata endpoints, or internal network resources.

MitigationUpdate the Eventin plugin to version 4.0.38 or later. If immediate patching is not possible, consider disabling or restricting access to the proxy_image functionality at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Eventin plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the eventin folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Eventin plugin folder exists in wp-content/plugins/ and the plugin is active
  2. Determine installed Eventin version
    Check the main plugin file (usually eventin.php or index.php) in the eventin folder for the 'Version' header in the plugin comment block, or view version in WordPress admin plugin list
    Affected if Installed version is lower than 4.0.38 (e.g., 4.0.37, 4.0.36, etc.)
  3. Verify proxy_image functionality is accessible
    Check if the WordPress AJAX endpoint for proxy_image exists by examining the plugin source code for AJAX action hooks (like wp_ajax_nopriv_proxy_image or similar) and confirm the function is not disabled
    Affected if The proxy_image function is hooked to a public (non-authenticated) AJAX action and is callable without authentication
  4. Check for suspicious outbound requests
    Review web server access logs and WordPress debug logs for unusual outgoing HTTP requests originating from the server, especially to internal IPs (10.x, 192.168.x, 172.16-31.x) or cloud metadata endpoints (169.254.169.254)
    Affected if Outbound requests to internal or metadata endpoints are present in logs and correlate with proxy_image usage

You are affected if the Eventin plugin is installed, active, and version is below 4.0.38 with the proxy_image function exposed to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Eventin plugin to version 4.0.38 or later. If immediate patching is not possible, consider disabling or restricting access to the proxy_image functionality at the web server level.

Recommended fix Moderate confidence

Eventin plugin version 4.0.38 or higher

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Eventin plugin (also described as 'The Events Calendar, Event Booking, Registrations and Event Tickets – Eventin')
  4. 4. Check the current installed version - if it is 4.0.37 or below, an update is needed
  5. 5. Update the plugin to the latest available version (version 4.0.38 or higher)
  6. 6. Verify the update completed successfully
  7. 7. Test that the plugin functionality remains working as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7813 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data