dbcve.org
Permalink Manager LiteWordPress extension · Permalink Manager Lite Project

CVE-2024-29092

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 2.4.3.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Maciej Bis Permalink Manager Lite allows Reflected XSS.This issue affects Permalink Manager Lite: from n/a through 2.4.3.

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

Reflected cross-site scripting (XSS) vulnerability in Permalink Manager Lite allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the web page. This occurs during web page generation when the plugin fails to properly neutralize special characters in HTTP request parameters before displaying them in the response.

MitigationProperly sanitize and escape all user-supplied input before reflecting it in output, using context-appropriate encoding functions (such as esc_html(), esc_attr() for WordPress) and implementing server-side input validation.

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
Permalink Manager LiteWordPress extension
Affected:< 2.4.3.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 Permalink Manager Lite plugin
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'permalink-manager' or 'permalink-manager-lite'. Check the main plugin file for the version number.
    Affected if The plugin is installed and the version is lower than 2.4.3.1
  2. Verify the installed version number
    Open the main plugin PHP file (such as 'permalink-manager.php' or 'permalink-manager-lite.php') and locate the 'Version' header in the plugin comments, or check the version reported in the WordPress admin plugins page.
    Affected if The reported version is less than 2.4.3.1
  3. Confirm the plugin is active
    Check the WordPress database 'wp_options' table for the option 'active_plugins', or view the plugins list in the WordPress admin panel to confirm the plugin status.
    Affected if The plugin appears in the active plugins list and the version is vulnerable
  4. Inspect HTTP request handling for reflected parameters
    Review plugin source code files, particularly those handling URI or request parameter processing (such as 'class-permalink-manager.php' or similar), for direct use of $_GET, $_POST, or $_REQUEST variables in output without sanitization functions like esc_html() or esc_attr().
    Affected if Code directly outputs request parameters without proper sanitization
  5. Check for signs of exploitation attempts
    Review web server access logs and WordPress debug logs for unusual query parameters in requests to your site, particularly parameters that might be reflected in pages (look for <script>, javascript:, or other XSS payloads in URL parameters).
    Affected if Recent logs show suspicious URL parameters containing XSS vectors being submitted to your site

Your environment is affected if Permalink Manager Lite is installed, active, and running at a version lower than 2.4.3.1, with the vulnerability requiring only that the plugin is active to be exploitable.

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

Properly sanitize and escape all user-supplied input before reflecting it in output, using context-appropriate encoding functions (such as esc_html(), esc_attr() for WordPress) and implementing server-side input validation.

Recommended fix High confidence

Permalink Manager Lite 2.4.3.1

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find Permalink Manager Lite
  4. Check if an update to version 2.4.3.1 or later is available
  5. If available, update the plugin to the latest version
  6. Verify the update was successful by checking the plugin version

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

Fix this in Permalink Manager Lite 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-29092 — 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-29092 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