• Today I received a Weekly Security Digest notification email in French.

    Previously it had always been in English. No changes have been made to the site by our staff.

    My WordPress language settings defined at /wp-admin/options-general.php specify English as the site’s default language.

    My relevant admin user’s preferred language setting is defined as “Site default”

    WPML is installed on the website for an alternate French version of the website but no modifications have been made to its settings that would allow it to translate outgoing emails.

    • ?? /wp-admin/admin.php?page=wpml-string-translation%2Fmenu%2Fstring-translation.php
    • ?? /wp-admin/admin.php?page=sitepress-multilingual-cms%2Fmenu%2Ftheme-localization.php

    Although outgoing emails are sent by WP Mail SMTP no modifications have been made to translate emails into another language from its settings or configuration.

    All other site notification emails are in english (eg: Password reset)

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hi @skunkworks,

    The Security Digest email is a so called scheduled email. The SolSec plugin scheduled emails check callback is hooked to the WordPress core init action. This means that there is a scheduled emails check performed on EVERY request to the site. If a scheduled email is due it gets send.

    Now it is possible to add some extra debug info at the bottom of every (non-user) email send. It is useful for identifying what site request triggered the email to be send (eg WP Cron job or a site request URL). You simply add the line below to the wp-config.php file:

    define( 'ITSEC_DEBUG', true );

    As an example, if an email being send was triggered by WP Cron you’ll find at the bottom of the email:

    Debug info (source page): WP-Cron

    Other source page values include WP-CLI, unknown or the full URL of the request that triggered the email to be send. The latter is probably what you’ll get to see by default in the Security Digest email. I guess that if the locale is set to France in the context of the request the email will be send in French language.

    Alternatively you can offload the SolSec plugin scheduled emails check to WP Cron by adding the line below to the wp-config.php file:

    define( 'ITSEC_NOTIFY_USE_CRON', true );

    Apart from the performance gain perhaps this will also help making the Security Digest email language more constant.

    +++ To prevent any confusion, I’m not SolidWP +++

    • This reply was modified 4 months, 2 weeks ago by nlpro.
    • This reply was modified 4 months, 2 weeks ago by nlpro.
    Thread Starter skunkworks

    (@skunkworks)

    Have added

    define( 'ITSEC_DEBUG', true );

    to the wp-config and will see what happens when the next Weekly Digest email comes in.

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @skunkworks, I just wanted to hop in here and confirm whether the suggestions by @nlpro helped resolve the problem. If not, let us know along with the steps you’ve tried.

    As always, we appreciate the help, @nlpro!?

    Thread Starter skunkworks

    (@skunkworks)

    Thanks for checking in on this. Strangely the Weekly report email didn’t come in. (Should’ve been on the 19th) Will need to check on why that is since I know site emails are working properly.

    Thread Starter skunkworks

    (@skunkworks)

    Checked the logs from the Post SMTP plugin and a weekly report email wasn’t sent.

    Checked the Solid security plugin’s settings for the security digest at:

    wp-admin/admin.php?page=itsec&path=%2Fsettings%2Fnotification-center%2Fdigest

    and all was as expected there. Not sure why the email wasn’t sent. Many other emails from WordPress have been sent in that time and are visible in the logs.

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @skunkworks, since you already enabled the Solid Security Debug menu, can you try clicking the “Reset” button under the Scheduler table on your Debug page?

    The under the Notification Center table, can you confirm that the “digest” ID has a schedule for “Next Send”?

    If you can send screenshots of the Debug page, that would be helpful.

    nlpro

    (@nlpro)

    Hi @skunkworks,

    Just wanted to add 2 relevant pieces of info:

    • Adding the ITSEC_DEBUG constant to the wp-config.php will also add a new Debug submenu option to the Solid Security plugin main Security menu. That is the Debug page @shanedelierrr is referring to.
    • The Security Digest email is not send when there is nothing to report (even when the Debug page shows that it’s scheduled). Which totally makes sense. Nothing to report means, there have not been any lockouts nor any detected file changes since the last send Security Digest email.

    Based on the fact that you changed the wp-config.php file, the File Change module should have picked up that change, consequently sending the Security Digest email. That is, if the File Change module is enabled!

    I know the last Security Digest was in French language, but (if not deleted yet) please check it’s content (use Google translate if you have to). The email content will tell us what security event/feature triggered that Security Digest email to be send (lockout(s) and/or file change(s)).

    • This reply was modified 4 months ago by nlpro.
    • This reply was modified 4 months ago by nlpro.
    nlpro

    (@nlpro)

    Hi @skunkworks,

    Please let us know if you need any further assistance. If not, share how you managed to resolve the issue and then simply mark this topic as ‘Resolved’.

    +++ To prevent any confusion, I’m not SolidWP +++

    Thread Starter skunkworks

    (@skunkworks)

    can you try clicking the “Reset” button under the Scheduler table on your Debug page?

    Done.

    under the Notification Center table, can you confirm that the “digest” ID has a schedule for “Next Send”?

    Reads:

    digest – Last Sent: 2024-09-26 20:08:05, Next Send: 2024-09-27 20:08:05, Schedule: daily (Just changed to daily by me) Also I clicked “Force” button which resulted in an email arriving (in English). Unfortunately the email reads:

    Site Scan
    An error occurred while running the scheduled site scan on [REDACTED SITE NAME]:
    Error Message: Unable to determine if the scan target is allowed: Target site returned invalid response. The site scanner was forbidden from accessing your site. Please check if the IP address 207.246.255.60 has been blocked.
    Error Code: site_verification_failed.connection_error

    Is https://ipinfo.io/207.246.255.60 Solid Security? If so, it was blocked by Cloudflare’s Firewall. You may want to get that IP whitelisted by Cloudflare’s staff as a known safe bot.

    I know the last Security Digest was in French language, but (if not deleted yet) please check it’s content (use Google translate if you have to). The email content will tell us what security event/feature triggered that Security Digest email to be send (lockout(s) and/or file change(s)).

    It was originally an IP block that was reported in French.

    Thread Starter skunkworks

    (@skunkworks)

    Update: Just received another Solid Security Email randomly in French.

    Translated:

    Main body:

    Site analysis

    Scheduled site scan found 1 issue [REDACTED-URL].ca/fr.

    Known vulnerabilities

    WordPress WPML Multilingual CMS plugin <= 4.6.12 – Authenticated (Contributor+) Remote Code Execution via Twig Server-Side Template Injection vulnerability

    Footer:

    Debugging information (source page): [REDACTED-URL].ca/fr

    The email was followed 12 hours later by an English version of the same email that differed slightly.

    Main body:

    Site Scan

    The scheduled site scan found 1 issue when scanning [REDACTED-URL].ca.

    Known Vulnerabilities

    WordPress WPML Multilingual CMS plugin <= 4.6.12 – Authenticated (Contributor+) Remote Code Execution via Twig Server-Side Template Injection vulnerability

    Footer:

    Debug info (source page): WP-Cron

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.