dbcve.org
Melapress File MonitorWordPress extension · Melapress

CVE-2025-3702

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-03
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in Melapress Melapress File Monitor website-file-changes-monitor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Melapress File Monitor: from n/a through < 2.2.0.

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 · moderate confidence

Missing Authorization vulnerability in the Melapress File Monitor WordPress plugin allows unauthenticated or improperly authorized users to access sensitive file monitoring functionality due to incorrectly configured access control security levels. The vulnerability exists in versions prior to 2.2.0.

MitigationUpdate Melapress File Monitor plugin to version 2.2.0 or later which contains proper authorization controls. Verify file monitoring functionality continues to work correctly after the update.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Melapress File MonitorWordPress extension
Affected:< 2.2.0

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

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

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 Melapress File Monitor plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Melapress File Monitor' or 'Melapress Melapress File Monitor' in the list of active and inactive plugins.
    Affected if The plugin appears in the WordPress installation's plugin list regardless of active/inactive status.
  2. Check installed plugin version
    In the WordPress admin Plugins page, click on the plugin name to view details, or inspect the main plugin file (typically file-monitor.php or similar in wp-content/plugins/) and look for the Version header in the plugin comments.
    Affected if The displayed version number is lower than 2.2.0 (for example, 2.1.x, 2.0.x, 1.x).
  3. Confirm plugin is active
    On the WordPress Plugins admin page, check if Melapress File Monitor shows as 'Active' under the plugin status column.
    Affected if The plugin is active and running on the WordPress site.
  4. Test file monitoring endpoint accessibility
    If you have access to the site filesystem, examine the plugin's PHP files in wp-content/plugins/ to identify AJAX endpoints or direct-access PHP files related to file monitoring. Attempt to access these endpoints without authentication (for example, by making a direct HTTP request to known plugin URLs).
    Affected if File monitoring functionality or data is accessible without requiring WordPress login credentials or proper user role verification.

You are affected if the Melapress File Monitor plugin is installed with a version lower than 2.2.0 and the file monitoring features can be accessed without proper authentication or authorization checks.

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
Upgrade available Upgrade to 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Update Melapress File Monitor plugin to version 2.2.0 or later which contains proper authorization controls. Verify file monitoring functionality continues to work correctly after the update.

Recommended fix High confidence

Melapress File Monitor 2.2.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Melapress File Monitor' in the plugin list
  4. Check if the current version is below 2.2.0
  5. If below 2.2.0, click 'Update Now' to update to the latest version, which should be 2.2.0 or higher
  6. Verify the update completed successfully and the plugin is functioning normally

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

Fix this in Melapress File Monitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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