LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22716: WordPress OOPSpam Anti-Spam Plugin <= 1.1.35 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Cross-Site Scripting vulnerability in OOPSpam OOPSpam Anti-Spam plugin <= 1.1.35 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-22716 is a medium-severity cross-site scripting issue in the WordPress OOPSpam Anti-Spam plugin through version 1.1.35. The cited record says exploitation requires an authenticated admin-level user and user interaction, reducing broad internet risk but still creating concern on shared or compromised WordPress administration environments.

Executive priority

Treat this as a normal-priority WordPress hygiene item unless the plugin is widely deployed or admin accounts are weakly controlled. It is not flagged as known exploited in the provided sources, but vulnerable admin interfaces can still become useful after credential compromise.

Technical view

The vulnerability is CWE-79 XSS in OOPSpam Anti-Spam for WordPress, reported as affecting versions <= 1.1.35. CVSS 3.1 is 5.9 with network access, low complexity, high privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the OOPSpam Anti-Spam plugin at version 1.1.35 or earlier. The bundle does not provide CPEs or a definitive fixed version, so teams should verify plugin inventory and vendor guidance directly.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates an attacker needs high privileges and user interaction, which makes opportunistic mass exploitation less likely than unauthenticated WordPress flaws.

Researcher notes

Evidence is sparse. The bundle identifies authenticated admin+ XSS in OOPSpam Anti-Spam <= 1.1.35 and provides CVSS/CWE metadata, but it does not name a fixed release, affected CPE, vulnerable parameter, or exploit status beyond KEV=false.

Mitigation direction

  • Identify WordPress sites using OOPSpam Anti-Spam.
  • Check whether installed versions are <= 1.1.35.
  • Review vendor, WordPress, or Patchstack guidance for fixed versions.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin if no safe version can be confirmed.
  • Limit and audit WordPress admin-level accounts.

Validation and detection

  • Inventory WordPress plugins across production and staging sites.
  • Confirm OOPSpam Anti-Spam version numbers from trusted administrative records.
  • Review admin accounts for unnecessary privileges or unknown users.
  • Check web and WordPress logs for suspicious admin activity.
  • Document whether each site is patched, disabled, or accepted risk.
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-22716 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
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-22716Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
OOPSpamOOPSpam Anti-Spamoopspam-anti-spam, 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.