dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-69152

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

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
Unauthenticated Cross Site Scripting (XSS) in Artale | Wedding Photography WordPress <= 2.2.2 versions.

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

An unauthenticated cross-site scripting (XSS) vulnerability exists in the Artale Wedding Photography WordPress theme versions 2.2.2 and below, allowing remote attackers to inject malicious scripts into the site without authentication.

MitigationUpdate the Artale theme to the latest version beyond 2.2.2 once a patch is released. If no patch is available, consider removing or replacing the theme with a secure alternative and apply web application firewall rules to block XSS attack patterns.

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

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
Low

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

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 if Artale theme is installed
    Navigate to Appearance > Themes in the WordPress admin dashboard and look for the Artale Wedding Photography theme in the installed themes list.
    Affected if The Artale theme appears in the themes list, regardless of whether it is the active theme.
  2. Check the installed theme version
    In the WordPress admin under Appearance > Themes, click on the Artale theme details. The version number is displayed in the theme information panel.
    Affected if The version displayed is 2.2.2 or lower.
  3. Verify the theme is active on the site
    Check the site's frontend or inspect the page source to confirm the Artale theme is being loaded. Alternatively, in the WordPress admin under Appearance > Themes, confirm the Artale theme is marked as 'Active'.
    Affected if The Artale theme is currently active on the WordPress site.
  4. Compare against affected version range
    Compare the installed version from step 2 against the affected range: version 2.2.2 and below.
    Affected if The installed version is 2.2.2 or any version number lower than 2.2.2.

A user is affected if the Artale Wedding Photography theme is installed on their WordPress site and the installed version is 2.2.2 or below, regardless of whether it is the active theme.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Artale theme to the latest version beyond 2.2.2 once a patch is released. If no patch is available, consider removing or replacing the theme with a secure alternative and apply web application firewall rules to block XSS attack patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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