CVE-2025-13438: CWE-352 Cross-Site Request Forgery (CSRF) in dienodigital Page Title, Description & Open Graph Updater
The Page Title, Description & Open Graph Updater plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.02. This is due to missing nonce validation on multiple AJAX actions including dieno_update_page_title. This makes it possible for unauthenticated attackers to update page titles and metadata via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-13438 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the 'Page Title, Description & Open Graph Updater' WordPress plugin developed by dienodigital, affecting all versions up to and including 1.02. The vulnerability stems from the absence of nonce validation on several AJAX endpoints, notably the dieno_update_page_title action. Nonce validation is a security mechanism in WordPress designed to ensure that requests are intentional and originate from legitimate users. Without this protection, attackers can craft malicious web pages or links that, when visited or clicked by an authenticated site administrator, trigger unauthorized AJAX requests to update page titles and metadata. This manipulation can alter how pages appear in search engine results or social media previews, potentially misleading users or damaging the site’s reputation. The attack vector requires no authentication but does require user interaction (clicking a link). The CVSS 3.1 base score is 4.3 (medium severity), reflecting the limited impact on confidentiality and availability but a direct impact on integrity. No patches or fixes have been linked yet, and no known exploits have been observed in the wild. The vulnerability is classified under CWE-352, which covers CSRF issues. Given the plugin’s role in managing SEO-related metadata, the integrity of site content is at risk, which can have downstream effects on user trust and search engine rankings.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of their web content. Unauthorized changes to page titles and metadata can misrepresent the organization’s brand, degrade search engine optimization (SEO), and potentially redirect or confuse users. This can lead to reputational damage, reduced web traffic, and loss of customer trust. Although the vulnerability does not directly compromise confidentiality or availability, the manipulation of metadata can be leveraged in broader social engineering or phishing campaigns targeting European users. Organizations in sectors with high reliance on web presence—such as e-commerce, media, and public services—may experience amplified impacts. Additionally, regulatory frameworks like GDPR emphasize data integrity and protection of user trust, so reputational harm could have indirect compliance consequences. The requirement for administrator interaction means that organizations with strong user awareness and security training may reduce risk, but those lacking such controls remain vulnerable.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first verify if they use the affected plugin and upgrade to a patched version once available. In the absence of an official patch, administrators can implement manual nonce validation on the AJAX endpoints by modifying the plugin code to include WordPress’s check_ajax_referer function. Restricting access to AJAX actions to authenticated users with appropriate capabilities can further reduce risk. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF patterns or unexpected AJAX requests. Administrators should be trained to recognize phishing attempts and avoid clicking untrusted links, especially while logged into WordPress admin panels. Regular security audits and plugin reviews can help identify similar issues proactively. Finally, monitoring site metadata for unexpected changes can provide early detection of exploitation attempts.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-13438: CWE-352 Cross-Site Request Forgery (CSRF) in dienodigital Page Title, Description & Open Graph Updater
Description
The Page Title, Description & Open Graph Updater plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.02. This is due to missing nonce validation on multiple AJAX actions including dieno_update_page_title. This makes it possible for unauthenticated attackers to update page titles and metadata via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Technical Analysis
CVE-2025-13438 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the 'Page Title, Description & Open Graph Updater' WordPress plugin developed by dienodigital, affecting all versions up to and including 1.02. The vulnerability stems from the absence of nonce validation on several AJAX endpoints, notably the dieno_update_page_title action. Nonce validation is a security mechanism in WordPress designed to ensure that requests are intentional and originate from legitimate users. Without this protection, attackers can craft malicious web pages or links that, when visited or clicked by an authenticated site administrator, trigger unauthorized AJAX requests to update page titles and metadata. This manipulation can alter how pages appear in search engine results or social media previews, potentially misleading users or damaging the site’s reputation. The attack vector requires no authentication but does require user interaction (clicking a link). The CVSS 3.1 base score is 4.3 (medium severity), reflecting the limited impact on confidentiality and availability but a direct impact on integrity. No patches or fixes have been linked yet, and no known exploits have been observed in the wild. The vulnerability is classified under CWE-352, which covers CSRF issues. Given the plugin’s role in managing SEO-related metadata, the integrity of site content is at risk, which can have downstream effects on user trust and search engine rankings.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of their web content. Unauthorized changes to page titles and metadata can misrepresent the organization’s brand, degrade search engine optimization (SEO), and potentially redirect or confuse users. This can lead to reputational damage, reduced web traffic, and loss of customer trust. Although the vulnerability does not directly compromise confidentiality or availability, the manipulation of metadata can be leveraged in broader social engineering or phishing campaigns targeting European users. Organizations in sectors with high reliance on web presence—such as e-commerce, media, and public services—may experience amplified impacts. Additionally, regulatory frameworks like GDPR emphasize data integrity and protection of user trust, so reputational harm could have indirect compliance consequences. The requirement for administrator interaction means that organizations with strong user awareness and security training may reduce risk, but those lacking such controls remain vulnerable.
Mitigation Recommendations
To mitigate this vulnerability, organizations should first verify if they use the affected plugin and upgrade to a patched version once available. In the absence of an official patch, administrators can implement manual nonce validation on the AJAX endpoints by modifying the plugin code to include WordPress’s check_ajax_referer function. Restricting access to AJAX actions to authenticated users with appropriate capabilities can further reduce risk. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF patterns or unexpected AJAX requests. Administrators should be trained to recognize phishing attempts and avoid clicking untrusted links, especially while logged into WordPress admin panels. Regular security audits and plugin reviews can help identify similar issues proactively. Finally, monitoring site metadata for unexpected changes can provide early detection of exploitation attempts.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-19T19:03:35.513Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699697f26aea4a407a3bdfc7
Added to database: 2/19/2026, 4:56:18 AM
Last enriched: 2/19/2026, 5:32:14 AM
Last updated: 2/21/2026, 12:18:21 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.