dbcve.org
Wp Free SslWordPress extension · Prasadkirpekar

CVE-2024-44020

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to after 1.2.6 or later.
See remediation →
94/100
Remediation priority · Urgent
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 prasadkirpekar WP Free SSL – Free SSL Certificate for WordPress and force HTTPS wp-free-ssl.This issue affects WP Free SSL – Free SSL Certificate for WordPress and force HTTPS: from n/a through <= 1.2.7.

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 Missing Authorization vulnerability exists in the WP Free SSL plugin for WordPress (versions up to 1.2.7). The plugin fails to properly verify user permissions before allowing access to administrative functions related to SSL certificate management and HTTPS enforcement settings. This could allow authenticated users with limited privileges to modify critical security configurations.

MitigationUpdate to the latest version of the WP Free SSL plugin when a patched release becomes available. Until then, restrict administrative access to only trusted, high-privilege users and audit existing user accounts for unnecessary permissions.

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
Wp Free SslWordPress extension
Affected:<= 1.2.6

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Verify WP Free SSL plugin is installed
    Log into WordPress admin panel, go to Plugins > Installed Plugins, and look for 'WP Free SSL' or 'Prasadkirpekar Wp Free Ssl' in the list. Note the installed version number displayed.
    Affected if Plugin is installed and version is 1.2.6 or lower
  2. Check installed plugin version number
    In the plugins list, locate the version number displayed under the plugin name. Alternatively, access the plugin files via FTP or file manager and open the main plugin file (usually wp-free-ssl.php or similar) to read the 'Version:' header comment.
    Affected if Version displayed is 1.2.6 or any version up to and including 1.2.6
  3. Audit WordPress user roles and capabilities
    In WordPress admin, go to Users > All Users. Review each user account and note their assigned role (Administrator, Editor, Author, Contributor, Subscriber). Pay particular attention to users with Editor, Author, or Contributor roles who should not have access to security settings.
    Affected if There are users with non-Administrator roles (Editor, Author, Contributor) who have access to the WordPress admin area
  4. Verify plugin admin pages are accessible to limited users
    Log in as a user with Editor or Author role. Attempt to access the WP Free SSL plugin settings page by navigating to Settings > WP Free SSL or a similar admin menu item. Observe whether access is granted without permission error.
    Affected if Lower-privilege users can access and modify SSL/HTTPS settings without Administrator authentication

Your environment is affected if the WP Free SSL plugin is installed with version 1.2.6 or lower AND you have users with non-Administrator roles who can access the plugin's administrative functions.

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 a release after 1.2.6
Interim mitigation

Update to the latest version of the WP Free SSL plugin when a patched release becomes available. Until then, restrict administrative access to only trusted, high-privilege users and audit existing user accounts for unnecessary permissions.

Recommended fix Moderate confidence

Version 1.2.7 or later (check WordPress plugin repository for latest release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "WP Free SSL" in the plugin list
  4. Check if an update is available and update to the latest version
  5. If no update is available in WordPress, download the latest version from the official WordPress plugin repository and reinstall

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

Fix this in Wp Free Ssl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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