CVE-2024-37257
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 Neutralization of Input During Web Page Generation (XSS or '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.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 · high confidenceReflected XSS vulnerability in Permalink Manager Lite WordPress plugin allows attackers to inject malicious JavaScript through unsanitized URL parameters that get reflected in page output without proper input neutralization.
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.4CVSS 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 Lite is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Permalink Manager Lite' in the list. Alternatively, check the /wp-content/plugins/ directory for the permalink-manager-lite folder.Affected if The plugin is present in the WordPress installation
-
Identify the installed versionIn the WordPress admin Plugins page, click on the plugin name to view details, or check the main plugin file (e.g., /wp-content/plugins/permalink-manager-lite/readme.txt) for the Version field in the file header.Affected if The version number is lower than 2.4.3.4 (e.g., 2.4.3.3, 2.4.2, etc.)
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the Permalink Manager Lite plugin shows as 'Active'. Only active plugins can process requests and expose the vulnerability.Affected if The plugin is active and running
-
Identify accessible URL parametersTest the site by accessing common WordPress URLs (homepage, posts, pages) and appending test parameters such as ?pm_nice_url= or ?pm- that may be processed by the plugin. Check the HTML source of the response to see if parameter values are reflected unsanitized.Affected if URL parameter values from the request appear in the page output without proper HTML encoding/escaping
If Permalink Manager Lite version is below 2.4.3.4 and the plugin is active, the site is potentially vulnerable to reflected XSS via URL parameters that get reflected in the page output.
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.4
Update to the latest version of Permalink Manager Lite when available, or implement proper output encoding/escaping on user-supplied parameters before reflecting them in HTML.
2.4.3.4
- 1. Back up your WordPress site (database and files) before making any changes
- 2. Navigate to WordPress Admin Dashboard > Plugins
- 3. Find 'Permalink Manager Lite' in the installed plugins list
- 4. Click 'Update now' if an update is available, or manually upload version 2.4.3.4 or later from the WordPress plugin repository
- 5. After update completes, verify the installed version is 2.4.3.4 or higher
- 6. Test that the plugin functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37257 — 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-37257 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