LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31620: WordPress CoverManager plugin <= 0.0.1 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in carperfer CoverManager covermanager allows Stored XSS.This issue affects CoverManager: from n/a through <= 0.0.1.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-31620 is a stored cross-site scripting issue in the WordPress CoverManager plugin through version 0.0.1. A lower-privileged user may be able to store malicious content that runs when another user views an affected page. Business impact depends on whether the plugin is installed and who can create CoverManager content.

Executive priority

Treat as a moderate web risk. Prioritize sites where untrusted users can submit or manage CoverManager content, especially public-facing WordPress properties with administrator sessions exposed to plugin-generated pages.

Technical view

The CVE describes CWE-79 improper input neutralization during web page generation in carperfer CoverManager. The CVSS 3.1 score is 6.5 with network attack vector, low complexity, low privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to WordPress sites running the CoverManager plugin version 0.0.1 or earlier. The provided data does not identify affected hosting platforms, themes, or other plugins.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is stored XSS, so impact likely requires an attacker with plugin-related input access and a victim viewing affected generated content.

Researcher notes

Evidence is narrow: CVE metadata and Patchstack identify stored XSS in CoverManager through 0.0.1, but the bundle does not include root cause details, a fixed version, exploit maturity, or proof-of-concept specifics. Avoid assuming broader WordPress impact.

Mitigation direction

  • Check Patchstack and vendor guidance for a fixed CoverManager release.
  • Update CoverManager if a vendor-supported fixed version is available.
  • Disable or remove CoverManager where it is not business-critical.
  • Restrict plugin content-management access to trusted users only.
  • Use WordPress security controls to monitor stored script-like content.

Validation and detection

  • Inventory WordPress sites for the CoverManager plugin.
  • Confirm installed CoverManager versions are not 0.0.1 or earlier.
  • Review roles allowed to create or edit CoverManager content.
  • Inspect stored plugin content for unexpected script-like markup.
  • Verify the plugin is updated, disabled, or removed per guidance.
Prepared
Confidence
medium
Sources
3

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-2025-31620 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.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-31620Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
carperferCoverManagercovermanager, 0unaffected
Weakness

CWE details

CWE-79

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