LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38326: Post Title Counter <= 1.1 Reflected Cross-Site Scripting

The Post Title Counter WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the notice parameter found in the ~/post-title-counter.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 1.1.

MediumCVSS 6.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-38326 is a reflected cross-site scripting issue in the Post Title Counter WordPress plugin through version 1.1. An attacker could cause script to run in a visitor’s browser if the visitor follows a maliciously crafted interaction. Business impact is most relevant for sites still running this old plugin version.

Executive priority

Treat this as a moderate-priority cleanup item. It is not listed as known exploited in the provided data, but exposed WordPress plugins create preventable website risk and should be removed or remediated promptly.

Technical view

The vulnerability is CWE-79 reflected XSS through the notice parameter in ~/post-title-counter.php. The CVSS 3.1 score is 6.1 with network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites with the Post Title Counter plugin installed at version 1.1 or earlier. The source bundle does not identify other affected products or CPEs.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The attack requires user interaction, which generally means phishing or social engineering is needed before browser-side impact occurs.

Researcher notes

Evidence supports reflected XSS in Post Title Counter up to and including 1.1. The bundle does not name a patched version, exploit activity, or vendor workaround, so remediation should be tied to current vendor or WordPress plugin repository guidance.

Mitigation direction

  • Inventory WordPress sites for the Post Title Counter plugin.
  • Disable or remove the plugin if it is not business-critical.
  • Check vendor or WordPress plugin guidance for a fixed release.
  • Apply an available vendor-supported update if one exists.
  • Use WAF or security plugin controls to reduce reflected XSS risk.

Validation and detection

  • Confirm whether Post Title Counter is installed on each WordPress site.
  • Verify installed versions are not 1.1 or earlier.
  • Review web logs for suspicious requests involving the notice parameter.
  • Confirm the plugin is removed, disabled, or updated per vendor guidance.
  • Document any remaining business need for continued plugin use.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2021-38326 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
Medium
CVSS
6.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:N

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
3Source 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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-38326Attack 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:N

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Post Title CounterPost Title Counter1.1Listed
Weakness

CWE details

CWE-79

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