dbcve.org
Wolf CmsApplication · Wolfcms

CVE-2019-25070

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to after 0.8.3.1 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
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in WolfCMS up to 0.8.3.1. It has been rated as problematic. This issue affects some unknown processing of the file /wolfcms/?/admin/user/add of the component User Add. The manipulation of the argument name leads to basic cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-135125 was assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

A stored cross-site scripting (XSS) vulnerability exists in WolfCMS up to version 0.8.3.1 within the admin panel's user add functionality at /wolfcms/?/admin/user/add. The 'name' parameter does not properly sanitize user input, allowing injection of malicious JavaScript that executes when administrators view the user list or user details.

MitigationSince WolfCMS is unsupported, migrate to a actively-maintained CMS or manually apply input validation/sanitization to the user name field in the source code, followed by comprehensive testing to confirm the XSS payload no longer executes.

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
Wolf CmsApplication
Affected:<= 0.8.3.1

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. Identify WolfCMS version
    Locate the WolfCMS installation directory and check the version.php or changelog file, typically found in the root directory or in a file named 'version' or 'changelog.txt' within the WolfCMS installation
    Affected if The installed version is 0.8.3.1 or lower (any version up to and including 0.8.3.1)
  2. Confirm admin panel access
    Navigate to the admin login page at /wolfcms/?/admin/ and verify you can access or attempt to log in to the WolfCMS administrative interface
    Affected if The admin panel is accessible and functional (the XSS payload would be injected here)
  3. Verify user management module exists
    After logging into the admin panel, check if the user management functionality is present by navigating to or finding a 'Users' or 'User' section in the admin navigation menu
    Affected if User management module exists and is enabled in the admin panel
  4. Inspect user name input handling
    Access the user add functionality at /wolfcms/?/admin/user/add (or equivalent) and examine how the 'name' parameter handles input, or use a browser developer tool to inspect the HTML form field for the user name input
    Affected if The 'name' field in the user add form does not appear to have input sanitization or encoding (the vulnerability exists here)

A user is affected if they have WolfCMS version 0.8.3.1 or lower installed, the admin panel is accessible, and the user management module is enabled without input sanitization on the name field.

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 a release after 0.8.3.1
Interim mitigation

Since WolfCMS is unsupported, migrate to a actively-maintained CMS or manually apply input validation/sanitization to the user name field in the source code, followed by comprehensive testing to confirm the XSS payload no longer executes.

Recommended fix Low confidence
  1. Wolf CMS (versions <= 0.8.3.1) is no longer supported by the maintainer according to the official CVE description.
  2. There is no vendor-provided patch or fixed version available for this vulnerability.
  3. Consider migrating to an actively maintained CMS solution as Wolf CMS has been abandoned.
  4. If continued use is mandatory, implement strict Content Security Policy (CSP) headers to mitigate XSS attacks, but this is not a complete remediation.
Caveat The product is end-of-life with no supported successor identified in the provided materials

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

Fix this in Wolf Cms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-25070 — 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-2019-25070 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