dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1657

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 EventPrime plugin for WordPress is vulnerable to unauthorized image file upload in all versions up to, and including, 4.2.8.4. This is due to the plugin registering the upload_file_media AJAX action as publicly accessible (nopriv-enabled) without implementing any authentication, authorization, or nonce verification despite a nonce being created. This makes it possible for unauthenticated attackers to upload image files to the WordPress uploads directory and create Media Library attachments via the ep_upload_file_media endpoint.

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 EventPrime WordPress plugin registers the upload_file_media AJAX action as publicly accessible without authentication, authorization, or proper nonce verification, allowing unauthenticated attackers to upload arbitrary image files to the WordPress uploads directory and create Media Library attachments.

MitigationDisable the nopriv access for the ep_upload_file_media AJAX action and implement nonce verification along with proper authentication checks and file type validation before allowing any uploads.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify EventPrime plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find EventPrime. Note the version number. Alternatively, check the plugin file at /wp-content/plugins/event-prime/ or via WP-CLI: wp plugin list --name=event-prime
    Affected if EventPrime plugin is installed and version falls within the affected range (if known); otherwise any unpatched version is potentially vulnerable
  2. Test AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=ep_upload_file_media, without providing any authentication cookies or nonce tokens. Use: curl -X POST 'https://yourdomain.com/wp-admin/admin-ajax.php' -d 'action=ep_upload_file_media'
    Affected if The request completes without returning a 401/403 authentication error, indicating the AJAX action is publicly accessible without auth
  3. Check for unauthorized Media Library uploads
    In WordPress admin, go to Media > Library. Look for image attachments with unusual timestamps, no associated author, or suspicious filenames. Query database: SELECT * FROM wp_posts WHERE post_type='attachment' ORDER BY post_date DESC LIMIT 20
    Affected if Unexpected or suspicious image attachments exist in the Media Library that were not uploaded by legitimate administrators
  4. Review server access logs for exploitation attempts
    Search web server logs (Apache/nginx) for requests to admin-ajax.php containing 'ep_upload_file_media'. Example grep: grep 'admin-ajax.php.*ep_upload_file_media' /var/log/apache2/access.log
    Affected if Log entries show POST requests to ep_upload_file_media from IPs other than trusted admin IPs, indicating potential exploitation attempts

The environment is affected if EventPrime plugin is installed and the ep_upload_file_media AJAX action responds to unauthenticated requests without requiring authentication or nonce verification.

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

Disable the nopriv access for the ep_upload_file_media AJAX action and implement nonce verification along with proper authentication checks and file type validation before allowing any uploads.

Recommended fix Moderate confidence

Upgrade to the latest version of EventPrime plugin (version higher than 4.2.8.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the EventPrime plugin
  4. 4. Check the current version number to confirm it is 4.2.8.4 or below
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest patched version
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the AJAX endpoint no longer responds to unauthenticated requests by confirming the upload_file_media action requires proper authorization

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1657 — 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-2026-1657 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