Post Pay CounterWordPress extension · Thecrowned
CVE-2023-47673
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Stefano Ottolenghi Post Pay Counter plugin <= 2.784 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 confidenceUnauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the Post Pay Counter WordPress plugin by Stefano Ottolenghi affecting versions 2.784 and below. The vulnerability allows attackers to inject malicious JavaScript scripts through unsanitized user input that gets reflected in the application's response, likely via URL parameters.
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 Pay CounterWordPress extension
<= 2.789CVSS 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.
-
Verify Post Pay Counter plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Post Pay Counter' in the list, or check the filesystem at /wp-content/plugins/Affected if The plugin is not installed or not present in the WordPress environment
-
Check the installed plugin versionIn WordPress admin, click on the Post Pay Counter plugin to view its details, or read the version from the plugin's main PHP file header in /wp-content/plugins/Affected if The installed version is 2.789 or lower, or any version that matches the range <= 2.789
-
Identify if URL parameters are reflected in responsesReview plugin code for functions that output $_GET, $_POST, or $_REQUEST parameters directly into HTML without sanitization (search for echo, print, or print_r with superglobal variables)Affected if The plugin code reflects any user-supplied input from URL parameters into HTML output without proper encoding or sanitization
-
Confirm the plugin is accessible to unauthenticated usersTest accessing pages using the Post Pay Counter functionality without logging in, or verify plugin public-facing code does not require authenticationAffected if The vulnerable endpoint or parameter is accessible without authentication (the CVE specifies this as unauthenticated reflected XSS)
You are affected if the Post Pay Counter plugin is installed with version 2.789 or lower and any URL parameters are reflected in responses without sanitization, especially on pages accessible to unauthenticated users.
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.
From vendor dataUpdate the Post Pay Counter plugin to the latest patched version beyond 2.784. If no update is available, apply input validation and output encoding to all user-supplied data reflected in HTTP responses.
Fix this in Post Pay Counter
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47673 — 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-2023-47673 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