Permalink Manager LiteWordPress extension · Permalink Manager Lite Project

CVE-2022-41781

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 2.2.20.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Broken Access Control vulnerability in Permalink Manager Lite plugin <= 2.2.20 on WordPress.

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

Broken Access Control vulnerability in Permalink Manager Lite WordPress plugin versions 2.2.20 and prior allows unauthorized users to potentially bypass authorization checks and access or modify permalink settings they should not have access to.

MitigationUpdate Permalink Manager Lite plugin to a version newer than 2.2.20. Verify all permalink configurations remain intact after update.

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.2.20.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Permalink Manager Lite is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Permalink Manager Lite' in the list
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In the Plugins list, view the version number displayed beneath the plugin name 'Permalink Manager Lite'
    Affected if Version shown is 2.2.20 or lower (vulnerable); version 2.2.20.1 or higher is fixed
  3. Inspect plugin files for version marker
    If admin access is limited, check the main plugin file (permalink-manager.php) in wp-content/plugins/permalink-manager-lite/ for the 'Version' header comment
    Affected if Version header reads 2.2.20 or lower
  4. Review user access to permalink settings
    Navigate to Permalink Manager settings panel (usually under Settings > Permalinks) and verify which user roles can access and modify permalink configurations
    Affected if Non-administrator users (such as editors or authors) can access or modify permalink settings without proper authorization

You are affected if the Permalink Manager Lite plugin is installed with version 2.2.20 or prior, allowing unauthorized users to access or modify permalink configurations they should not be able to change.

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.

From vendor data
Upgrade available Upgrade to 2.2.20.1 or later
Fixed in 2.2.20.1
Interim mitigation

Update Permalink Manager Lite plugin to a version newer than 2.2.20. Verify all permalink configurations remain intact after update.

Fix this in Permalink Manager Lite Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41781 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41781 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