Melapress Login SecurityWordPress extension · Melapress
CVE-2024-35650
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Melapress MelaPress Login Security melapress-login-security.This issue affects MelaPress Login Security: from n/a through <= 1.3.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 confidenceA PHP Remote File Inclusion vulnerability exists in MelaPress Login Security plugin versions through 1.3.0, where improper control of filename for include/require statements allows attackers to include remote malicious files, potentially leading to arbitrary code execution on the affected WordPress server.
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 Login SecurityWordPress extension
< 1.3.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify MelaPress Login Security plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Melapress Login Security' or 'MelaPress Login Security' in the plugin list.Affected if The plugin named 'Melapress Login Security' or 'MelaPress Login Security' appears in the installed plugins list.
-
Check installed plugin versionIn the Plugins list, locate Melapress Login Security and note the version number displayed beneath the plugin name.Affected if The displayed version number is lower than 1.3.1 (for example: 1.3.0, 1.2.0, 1.0.0, etc.).
-
Confirm plugin is activeIn the Plugins list, verify that the 'Melapress Login Security' plugin has an 'Active' status indicator.Affected if The plugin is both installed AND active (an inactive plugin with a vulnerable version is not directly exploitable).
A user is affected if they have the Melapress Login Security plugin installed, it is currently active, and the installed version is lower than 1.3.1.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.1
Update MelaPress Login Security to the latest patched version immediately, or if no patch exists, review and sanitize all file inclusion paths in the plugin code to prevent remote file inclusion.
1.3.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate Melapress Login Security in the plugin list
- Check if the current version is below 1.3.1
- If vulnerable, click 'Update Now' to update to the latest version, or manually download version 1.3.1 from the WordPress plugin repository
- After update, verify the plugin is running version 1.3.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Melapress Login Security
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-35650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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