CVE-2024-2738
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 · uneditedThe Permalink Manager Lite and Pro plugins for WordPress are vulnerable to Reflected Cross-Site Scripting via the ‘s’ parameter in multiple instances in all versions up to, and including, 2.4.3.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 · high confidenceThe Permalink Manager Lite and Pro WordPress plugins (versions up to 2.4.3.1) contain a reflected XSS vulnerability in the 's' parameter due to insufficient input sanitization and output escaping. Unauthenticated attackers can inject arbitrary JavaScript through crafted URLs that execute when users click malicious links.
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< 2.4.3.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Permalink Manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Permalink Manager Lite' or 'Permalink Manager Pro'. Alternatively, check the /wp-content/plugins/ directory for folders starting with 'permalink-manager'.Affected if Either Lite or Pro version of the plugin is installed
-
Identify the installed version numberIn WordPress admin > Plugins, click 'View Details' on the Permalink Manager plugin to see the installed version number. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment block.Affected if Version is less than 2.4.3.2 (any version up to and including 2.4.3.1 is vulnerable)
-
Verify the search functionality is accessibleThe vulnerability exists in the 's' parameter used for search functionality. Try accessing a page on the site with a URL containing ?s= parameter to confirm the search feature is active. Check WordPress permalink settings under Settings > Permalinks to confirm the plugin's functionality is enabled.Affected if The plugin's search-related features are active and accessible on the site
The site is affected if Permalink Manager Lite or Pro is installed with a version below 2.4.3.2 and the search functionality is accessible.
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 · scoped2.4.3.2
Update Permalink Manager Lite and Pro plugins to version 2.4.3.2 or later to obtain the patched version with proper input sanitization and output escaping for the 's' parameter.
Permalink Manager Lite version 2.4.3.2
- Backup your WordPress site database and files before updating
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate 'Permalink Manager Lite' in the plugin list
- If an update is available, click 'Update now' to install version 2.4.3.2
- Alternatively, manually download version 2.4.3.2 from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
- After updating, verify the plugin version shows 2.4.3.2 in the installed plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2738 — 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-2738 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