dbcve.org
Mantenimiento WebWordPress extension · Webartesanal

CVE-2022-38075

MEDIUM · 6.1 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 0.14 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability leading to Stored Cross-Site Scripting (XSS) in Mantenimiento web plugin <= 0.13 on WordPress.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Mantenimiento web WordPress plugin (version 0.13 and below) allows attackers to trick authenticated administrators into submitting malicious requests that store harmful scripts in the database, leading to Stored XSS when other users view affected pages.

MitigationUpgrade Mantenimiento web plugin to version > 0.13, which should include proper CSRF token validation on all state-changing operations to prevent unauthorized requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mantenimiento WebWordPress extension
Affected:< 0.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Mantenimiento web plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Mantenimiento web' or 'Webartesanal Mantenimiento Web'
    Affected if The plugin is not found in the installed plugins list
  2. Check installed plugin version
    In the Plugins list, click on the plugin name to view its details, or inspect the plugin header in wp-content/plugins/mantenimiento-web/mantenimiento.php for the 'Version' field
    Affected if The version displayed is 0.13 or lower
  3. Confirm plugin is active
    In the Plugins list, verify that Mantenimiento web shows as 'Active' under the plugin status column
    Affected if The plugin is active and running
  4. Inspect stored plugin settings for malicious scripts
    Navigate to the plugin settings page (usually under Settings > Mantenimiento Web or a dedicated Mantenimiento Web admin menu) and examine all text fields, message fields, or content areas where user input is saved. View the page source to detect any injected script tags
    Affected if Any <script> tags, javascript: URIs, or other XSS payloads are present in the plugin configuration fields

A user is affected if the Mantenimiento web plugin version 0.13 or lower is installed, active, and contains unauthorized script content stored in its settings, indicating exploitation of the CSRF-to-Stored-XSS flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.14 or later
Fixed in 0.14
Interim mitigation

Upgrade Mantenimiento web plugin to version > 0.13, which should include proper CSRF token validation on all state-changing operations to prevent unauthorized requests.

Recommended fix High confidence

Version 0.14

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Mantenimiento Web' plugin in the list
  4. Click 'Update now' if an update is available, or manually update to version 0.14
  5. Verify the plugin updated successfully by checking the version number
  6. Test the plugin functionality to ensure it works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mantenimiento Web Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38075 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data