dbcve.org
Htaccess File EditorWordPress extension · Wpchill

CVE-2024-49256

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.0.19 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
Incorrect Authorization vulnerability in WP Chill Htaccess File Editor htaccess-file-editor allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Htaccess File Editor: from n/a through <= 1.0.18.

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

The WP Chill Htaccess File Editor WordPress plugin (versions <=1.0.18) contains an incorrect authorization vulnerability that allows users to access functionality not properly constrained by access control lists. This likely enables unauthenticated or lower-privileged users to access the htaccess file editor functionality, potentially allowing unauthorized modification of server configuration files.

MitigationUpdate the plugin to the latest version if a patched release is available; if no patch exists, disable the plugin or implement compensating controls such as restricting access to administrative functions at the server or WordPress role level.

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
Htaccess File EditorWordPress extension
Affected:< 1.0.19

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 the plugin is installed
    Check if the WP Chill Htaccess File Editor plugin exists in your WordPress installation. Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins directory for a folder named 'htaccess-file-editor' or similar.
    Affected if the plugin folder exists in the WordPress plugins directory
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate the WP Chill Htaccess File Editor entry. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comments.
    Affected if the displayed version number is lower than 1.0.19 (for example, 1.0.18, 1.0.17, etc.)
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that the WP Chill Htaccess File Editor shows as 'Active' under the plugin status column.
    Affected if the plugin shows an 'Active' status
  4. Verify user role exposure (optional context)
    Review which WordPress roles have access to the plugin functionality. The vulnerability allows users with lower privileges (such as subscribers or contributors) to access htaccess editor functionality that should be restricted to administrators.
    Affected if non-administrator roles have access to the htaccess file editor interface or functionality

You are affected if the WP Chill Htaccess File Editor plugin is installed, active, and running at version 1.0.18 or lower.

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 1.0.19 or later
Fixed in 1.0.19
Interim mitigation

Update the plugin to the latest version if a patched release is available; if no patch exists, disable the plugin or implement compensating controls such as restricting access to administrative functions at the server or WordPress role level.

Recommended fix Moderate confidence

1.0.19

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to WordPress admin dashboard > Plugins section
  3. Locate the 'Htaccess File Editor' plugin
  4. Click 'Update now' if version 1.0.19 is available, or update to the latest version from the WordPress plugin repository
  5. Verify the plugin updated successfully to version 1.0.19 or latest
  6. Test that the plugin functionality works as expected after the update

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

Fix this in Htaccess File Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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