LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47673: WordPress Post Pay Counter Plugin <= 2.784 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Stefano Ottolenghi Post Pay Counter plugin <= 2.784 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-47673 affects the WordPress Post Pay Counter plugin and allows unauthenticated reflected cross-site scripting when a user is tricked into interacting with a crafted request. Business impact is mainly session theft, content manipulation, or actions performed in a victim’s browser, especially if an administrator is targeted.

Executive priority

Treat this as a timely WordPress plugin remediation item, especially for public sites with multiple authors or administrators. It is high severity, but current provided evidence does not prove active exploitation.

Technical view

The source bundle describes CWE-79 reflected XSS in Stefano Ottolenghi Post Pay Counter, with CVSS 3.1 score 7.1: network exploitable, low complexity, no privileges required, user interaction required, scope changed, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the vulnerable Post Pay Counter plugin. The bundle says versions <= 2.784, while the Patchstack URL references 2.789, so version boundaries should be verified against vendor or Patchstack records.

Exploitation context

The bundle does not report CISA KEV listing or confirmed active exploitation. Exploitation requires user interaction, consistent with reflected XSS, and would be most damaging if a privileged WordPress user follows the attacker-controlled request.

Researcher notes

Source evidence is sparse and has a version inconsistency: the bundle states <= 2.784, while the Patchstack URL references 2.789. Do not assume exploit availability or fixed versions without checking the linked vulnerability record or vendor release notes.

Mitigation direction

  • Inventory WordPress sites for the Post Pay Counter plugin.
  • Verify installed plugin versions against official vendor or Patchstack guidance.
  • Update the plugin if a fixed version is available from trusted sources.
  • Restrict or disable the plugin if no safe update is confirmed.
  • Monitor WordPress admin activity for suspicious browser-driven changes.

Validation and detection

  • Check WordPress plugin inventory for package name post-pay-counter.
  • Record exact installed version on each affected WordPress site.
  • Compare findings with the CVE and Patchstack vulnerability entry.
  • Confirm remediation through plugin version review after update or removal.
  • Review web logs for unusual requests targeting plugin parameters.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47673 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-47673Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Stefano OttolenghiPost Pay Counterpost-pay-counter, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.