dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-32523

HIGH · 8.1 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in EverPress Mailster mailster.This issue affects Mailster: from n/a through <= 4.0.6.

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

A PHP Remote File Inclusion (RFI) vulnerability in the Mailster WordPress plugin (versions up to 4.0.6) allows attackers to include malicious remote files via improperly validated user input in include/require statements. This can lead to remote code execution on the affected WordPress installation.

MitigationUpdate Mailster plugin to the latest patched version immediately. If no patch is available, disable the plugin and review source code for unsafe use of include/require with user-supplied parameters.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/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. Locate the Mailster plugin installation directory
    Check your WordPress site's wp-content/plugins folder for a folder named 'mailster' or 'newsletter'
    Affected if The mailster plugin folder exists on the server
  2. Determine the installed Mailster version
    Open the main plugin file (usually mailster.php) and look for the 'Version:' header in the plugin comments, or check the version defined in the plugin code
    Affected if The reported version number is 4.0.6 or lower
  3. Compare version against the affected range
    Parse the version number found and verify it is less than or equal to 4.0.6
    Affected if The installed version is 4.0.6 or any version below it (e.g., 4.0.5, 4.0.0, 3.x)
  4. Verify the plugin is active
    Check WordPress admin under Plugins > Installed Plugins, or query the wp_options table for option_name 'active_plugins' containing 'mailster'
    Affected if The Mailster plugin is currently activated on the WordPress site

A user is affected if they have the Mailster WordPress plugin installed with any version numbered 4.0.6 or below and the plugin is active, as this version range contains the vulnerable include/require code paths.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Mailster plugin to the latest patched version immediately. If no patch is available, disable the plugin and review source code for unsafe use of include/require with user-supplied parameters.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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