Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10182: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in john-ackers dbview

0
Medium
VulnerabilityCVE-2025-10182cvecve-2025-10182cwe-79
Published: Tue Sep 30 2025 (09/30/2025, 03:35:30 UTC)
Source: CVE Database V5
Vendor/Project: john-ackers
Product: dbview

Description

The dbview plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'dbview' shortcode in all versions up to, and including, 0.5.5 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 18:14:40 UTC

Technical Analysis

CVE-2025-10182 is a stored Cross-Site Scripting (XSS) vulnerability identified in the john-ackers dbview plugin for WordPress, affecting all versions up to and including 0.5.5. The root cause is insufficient sanitization and output escaping of user-supplied attributes within the plugin's 'dbview' shortcode, which allows authenticated users with contributor-level or higher privileges to inject arbitrary JavaScript code into pages. When other users access these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or data theft. The vulnerability is classified under CWE-79, which pertains to improper neutralization of input during web page generation. The CVSS 3.1 base score is 6.4, reflecting a medium severity level, with an attack vector over the network, low attack complexity, requiring privileges (authenticated contributor or above), no user interaction, and a scope change due to affecting other users. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk to WordPress sites using this plugin, especially those with multiple contributors or editors. The lack of available patches at the time of publication necessitates immediate attention to mitigate potential exploitation.

Potential Impact

The primary impact of this vulnerability is the compromise of confidentiality and integrity of user data and sessions on affected WordPress sites. Attackers with contributor-level access can inject malicious scripts that execute in the browsers of other users, potentially leading to session hijacking, theft of sensitive information, or unauthorized actions performed on behalf of victims. Since the vulnerability does not affect availability, denial-of-service is unlikely. However, the scope change means that the attacker’s privileges can indirectly affect other users, increasing the risk profile. Organizations relying on the dbview plugin, especially those with multiple authenticated users, face risks of reputational damage, data breaches, and unauthorized access. The medium CVSS score reflects that while exploitation requires some privileges, the attack is relatively easy to perform and can have widespread consequences if exploited on high-traffic or sensitive sites.

Mitigation Recommendations

1. Immediate mitigation involves restricting contributor-level and higher user permissions to trusted individuals only, minimizing the risk of malicious script injection. 2. Disable or remove the dbview plugin until a patched version is released. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious script injections in the 'dbview' shortcode parameters. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected sites. 5. Monitor site pages for unexpected script content or unusual user behavior indicative of exploitation. 6. Educate site administrators and contributors about the risks of injecting untrusted content. 7. Once available, promptly apply official patches or updates from the plugin vendor. 8. Conduct regular security audits and vulnerability scans focusing on WordPress plugins and user-generated content. These measures go beyond generic advice by focusing on access control, proactive detection, and layered defenses specific to the nature of this stored XSS vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-09T14:35:31.939Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68db52aea473ffe031e4479d

Added to database: 9/30/2025, 3:46:54 AM

Last enriched: 2/27/2026, 6:14:40 PM

Last updated: 3/22/2026, 12:01:44 AM

Views: 75

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses