LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25461: WordPress Wp-Insert Plugin <= 2.5.0 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in namithjawahar Wp-Insert plugin <= 2.5.0 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-25461 is a stored cross-site scripting issue in the WordPress Wp-Insert plugin through version 2.5.0. It requires an authenticated administrator-level user and another user interaction, so it is not a simple remote takeover. Risk is higher where admin accounts are shared, delegated, or compromised.

Executive priority

Treat this as a moderate-priority WordPress plugin risk. Prioritize sites with many administrators, third-party site managers, or signs of account compromise. It should not outrank unauthenticated critical vulnerabilities, but it should be remediated during normal vulnerability cycles.

Technical view

The issue is CWE-79 stored XSS in namithjawahar Wp-Insert <= 2.5.0. CVSS 3.1 is 5.9 with network access, low complexity, high privileges required, user interaction required, and changed scope. The source bundle does not name a fixed version or specific affected code path.

Likely exposure

Exposure is limited to WordPress sites running the Wp-Insert plugin at version 2.5.0 or earlier. Practical risk depends on whether untrusted, delegated, or compromised admin-level accounts can reach the vulnerable plugin functionality.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not claim active exploitation. Exploitation requires authenticated admin-level access and user interaction, consistent with a post-authentication stored XSS scenario rather than unauthenticated mass exploitation.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE-79 classification, and Patchstack reference. No exploit details, affected code path, fixed version, or active exploitation evidence is provided in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for the Wp-Insert plugin and installed version.
  • Restrict plugin administration to trusted, necessary administrator accounts only.
  • Review Patchstack and vendor guidance for a fixed release or official workaround.
  • Disable or replace the plugin if no maintained fix is available.
  • Audit administrator accounts for unnecessary access and weak authentication controls.

Validation and detection

  • Confirm whether Wp-Insert is installed on each WordPress site.
  • Check whether the installed plugin version is 2.5.0 or earlier.
  • Review recent plugin configuration changes by administrator accounts.
  • Check logs for unexpected administrator activity or suspicious stored content changes.
  • Verify remediation by confirming removal, replacement, or vendor-supported fixed status.
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-25461 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-25461Attack 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
namithjawaharWp-Insertwp-insert, 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.