CVE-2024-27971
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 Premmerce Premmerce Permalink Manager for WooCommerce woo-permalink-manager.This issue affects Premmerce Permalink Manager for WooCommerce: from n/a through <= 2.3.10.
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 confidenceThis is a PHP Remote File Inclusion (RFI) vulnerability in the Premmerce Permalink Manager for WooCommerce plugin. The vulnerability allows attackers to include remote files via improperly validated user input in PHP include/require statements, potentially leading to arbitrary code execution on the server.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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 Premmerce Permalink Manager for WooCommerce is installedCheck your WordPress plugins directory (wp-content/plugins/) for the premmerce-permalink-manager-for-woocommerce folder, or list installed plugins via WP-CLI: wp plugin list --name='permalink-manager-for-woocommerce'Affected if The plugin folder or listing exists in your WordPress installation
-
Identify installed plugin versionCheck the main plugin PHP file header for the Version comment, typically in premmerce-permalink-manager-for-woocommerce.php, or run: wp plugin get permalink-manager-for-woocommerce --field=versionAffected if Version is lower than the patched release (check against vendor security advisory)
-
Confirm plugin is activeRun: wp plugin is-active permalink-manager-for-woocommerce, or check via WordPress admin Plugins pageAffected if Plugin status shows as active
-
Inspect for suspicious uploaded filesReview the plugin's upload directories and any file that handles include/require statements. Check wp-content/uploads/ and plugin subdirectories for unfamiliar .php files with names like tmp, include, or remote access patternsAffected if Unexpected PHP files exist that were not part of the original plugin package
-
Check server access logs for RFI patternsReview web server access logs (apache2 access.log, nginx access.log) for requests to the plugin containing remote URLs in query parameters, such as ?file=http:// or ?load=ftp://Affected if Logs show requests with external URLs being passed to the plugin's file inclusion functions
You are affected if the Premmerce Permalink Manager for WooCommerce plugin is installed, active, and running a version prior to the vendor patch.
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.
From vendor dataUpdate the plugin to the latest version which should contain proper input validation on file inclusion functions to prevent unauthorized file inclusion. If no update is available, disable the plugin until a patch is released.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27971 — 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-27971 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