LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25795: WordPress Feed Changer Plugin <= 0.2 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Cross-Site Scripting (XSS) vulnerability in WP-master.Ir Feed Changer & Remover plugin <= 0.2 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-25795 affects the WordPress Feed Changer & Remover plugin up to version 0.2. It is an authenticated administrator-level cross-site scripting issue. Business urgency is moderate: exposure is narrow because administrator access and user interaction are required, but successful abuse could affect confidentiality, integrity, and availability at a limited level.

Executive priority

Treat this as a targeted WordPress hygiene item, not an emergency internet-wide incident. Prioritize validation on public WordPress properties and any site with broad administrator access or weak account controls.

Technical view

The issue is CWE-79 cross-site scripting in WP-master.ir Feed Changer & Remover for WordPress, package feed-changer, version 0.2 and earlier. CVSS 3.1 is 5.9 with network attack vector, low complexity, high privileges, required user interaction, changed scope, and low CIA impact.

Likely exposure

Likely exposure is limited to WordPress sites that installed Feed Changer & Remover, also identified as feed-changer, at version 0.2 or earlier. The source bundle does not identify other affected products or versions.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates an authenticated administrator-level attacker and user interaction are required, reducing broad internet-scale risk compared with unauthenticated WordPress flaws.

Researcher notes

Evidence is limited to the CVE bundle and Patchstack reference. Do not assume a public exploit, patch availability, or broader product impact from the provided data. Validate exposure by plugin identity and version, then follow vendor or Patchstack remediation guidance.

Mitigation direction

  • Inventory WordPress sites for Feed Changer & Remover or the feed-changer package.
  • If version 0.2 or earlier is present, check vendor or Patchstack guidance before continued use.
  • Limit WordPress administrator access to trusted accounts only.
  • Review administrator accounts for unnecessary privileges and remove stale access.
  • Monitor affected sites for unexpected plugin configuration or content changes.

Validation and detection

  • Confirm whether Feed Changer & Remover is installed on each WordPress site.
  • Record the installed plugin version and compare it with the affected range of 0.2 or earlier.
  • Check whether administrator access is restricted and auditable.
  • Review WordPress logs for recent administrative changes involving the plugin.
  • Document findings and remediation decisions for affected sites.
Prepared
Confidence
high
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-25795 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-25795Attack 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
WP-master.irFeed Changer & Removerfeed-changer, 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.