dbcve.org
Post Status Notifier LiteWordPress extension · Ifeelweb

CVE-2023-47766

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 1.11.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 Timo Reith Post Status Notifier Lite plugin <= 1.11.0 versions.

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

Cross-site scripting (XSS) vulnerability in the Post Status Notifier Lite WordPress plugin versions 1.11.0 and below allows attackers to inject malicious scripts into web pages generated by the plugin through improper input neutralization.

MitigationUpdate the Post Status Notifier Lite plugin to a version beyond 1.11.0. If no update is available, consider removing the plugin or implementing additional output encoding/sanitization around plugin output.

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
Post Status Notifier LiteWordPress extension
Affected:< 1.11.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. Verify Post Status Notifier Lite is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Post Status Notifier Lite' by Ifeelweb in the list.
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In the Plugins list, locate Post Status Notifier Lite and note the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file (e.g., /wp-content/plugins/post-status-notifier-lite/post-status-notifier-lite.php) and look for the 'Version' header in the plugin comments.
    Affected if Version is 1.11.0 or below (any version less than 1.11.1)
  3. Identify usage of plugin-generated output
    Search WordPress pages, posts, and widget areas for shortcodes such as [psn_lite] or any custom output generated by the plugin. Check Appearance > Widgets for any Post Status Notifier widgets placed on the site.
    Affected if The plugin is actively generating front-end output through shortcodes or widgets
  4. Review plugin configuration settings
    Navigate to Settings > Post Status Notifier in WordPress admin. Review any custom notification rules, custom status definitions, or email templates that may contain user-supplied data rendered in public-facing pages.
    Affected if Custom plugin settings are configured and visible on the site front end

You are affected if Post Status Notifier Lite version 1.11.0 or below is installed AND the plugin is actively generating output on your website through shortcodes, widgets, or notification pages.

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

Update the Post Status Notifier Lite plugin to a version beyond 1.11.0. If no update is available, consider removing the plugin or implementing additional output encoding/sanitization around plugin output.

Recommended fix High confidence

1.11.1

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Post Status Notifier Lite' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.11.1
  5. 5. Alternatively, download version 1.11.1 from the WordPress Plugin Repository or the vendor
  6. 6. Deactivate the current plugin version, then delete it
  7. 7. Upload and install the new version 1.11.1
  8. 8. Reactivate the plugin

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

Fix this in Post Status Notifier Lite Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47766 — 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-2023-47766 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