dbcve.org
Wp TemplataWordPress extension · Hasthemes

CVE-2025-26917

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to 1.0.8 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in HasThemes WP Templata wptemplata allows Reflected XSS.This issue affects WP Templata: from n/a through <= 1.0.7.

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 · moderate confidence

Reflected XSS vulnerability in HasThemes WP Templata WordPress plugin allows attackers to inject malicious scripts through unsanitized user input that gets rendered in web pages without proper output encoding.

MitigationUpdate to the latest patched version of WP Templata when released; until then, implement WAF rules or input validation on the affected parameters to block script injection attempts.

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
Wp TemplataWordPress extension
Affected:< 1.0.8

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 WP Templata plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'HasThemes WP Templata' or check the plugin files in /wp-content/plugins/ for the templata folder
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed version number
    In WordPress admin Plugins list, find WP Templata and view the version number, or check the main plugin file (typically templata.php) for the 'Version' header comment
    Affected if Version is less than 1.0.8 or version cannot be determined (indicating outdated release)
  3. Identify exposed frontend parameters
    Review the plugin source code for PHP files that read $_GET, $_POST, or $_REQUEST variables and output them to HTML without sanitization functions like esc_html() or esc_attr()
    Affected if The plugin accepts user input via URL parameters and reflects it back into page output without encoding
  4. Check for suspicious requests in logs
    Search web server access logs for requests to pages using the plugin with script tags in query parameters (e.g., <script>alert(1)</script>)
    Affected if Malicious XSS payloads appear in logs targeting the plugin's input parameters

If WP Templata plugin is active, running, and version is below 1.0.8, the environment is potentially affected by this reflected XSS vulnerability.

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 1.0.8 or later
Fixed in 1.0.8
Interim mitigation

Update to the latest patched version of WP Templata when released; until then, implement WAF rules or input validation on the affected parameters to block script injection attempts.

Recommended fix Moderate confidence

WP Templata version 1.0.8

  1. 1. Back up your WordPress site (database and files) before making any changes
  2. 2. Navigate to WP Admin > Plugins > Installed Plugins
  3. 3. Locate the 'WP Templata' plugin by HasThemes
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.0.8
  5. 5. Alternatively, you can manually upload version 1.0.8 of the plugin from the WordPress repository or vendor
  6. 6. After updating, clear any caching plugins and test that the site functions correctly
  7. 7. Verify the XSS vulnerability is remediated by confirming the fix addresses the reflected XSS in the plugin

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

Fix this in Wp Templata Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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