LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45772: WordPress Proofreading Plugin <= 1.0.11 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Scribit Proofreading plugin <= 1.0.11 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress Proofreading plugin by Scribit. Versions up to 1.0.11 are reported vulnerable to unauthenticated reflected cross-site scripting. A successful attack would still require user interaction, but could let an attacker run script in a visitor or administrator browser context.

Executive priority

Treat this as a high-priority WordPress exposure check, not an emergency internet-wide incident based on the supplied evidence. The business risk is browser-session compromise or content manipulation if an administrator or user is induced to interact with malicious content.

Technical view

The sources describe CWE-79 reflected XSS in the proofreading WordPress package, affecting Proofreading <= 1.0.11. CVSS 3.1 is 7.1 with network access, low complexity, no privileges, required user interaction, and changed scope. The bundle does not include endpoint, payload, exploit telemetry, or fixed-version details.

Likely exposure

Exposure is limited to WordPress sites with the Scribit Proofreading plugin installed at version 1.0.11 or earlier. The bundle provides no CPEs and lists packageName as proofreading, so confirm by WordPress plugin inventory rather than platform-wide assumptions.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The attack class is reflected XSS, so realistic exploitation depends on getting a target user to follow attacker-controlled content that reaches the vulnerable plugin behavior.

Researcher notes

Evidence is sparse. Patchstack and CVE metadata support the vulnerability class, severity, and affected version boundary, but not exploit details, patch availability, or observed exploitation. Avoid assuming all WordPress sites are affected; validate plugin presence and active status.

Mitigation direction

  • Inventory WordPress sites for the Proofreading plugin.
  • Confirm whether installed versions are 1.0.11 or earlier.
  • Check Scribit, WordPress, and Patchstack guidance for a fixed release.
  • Update promptly if a vendor-supported fixed version is available.
  • Disable or remove the plugin where no safe update is available.
  • Prioritize administrator-facing sites and high-trust user workflows.

Validation and detection

  • Review plugin inventories across production and staging WordPress instances.
  • Verify exact plugin version and whether the plugin is active.
  • Check vendor advisories for fixed-version or retirement status.
  • Review web logs for unusual requests involving the plugin.
  • Confirm no vulnerable version remains enabled after remediation.
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-45772 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-45772Attack 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
ScribitProofreadingproofreading, 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.