Security Alert: 26 BuddyDev accounts compromized in brute force attack.

BuddyDev

Search

Replies

  • Participant
    Level: Initiated
    Posts: 6
    Matt on January 18, 2022 at 1:13 am #42656

    Ugh….Thank you, Brajesh. It was actually a caching setting on our server (Redis in our case). I deactivated and everything started to make sense.

    Thanks again!
    Matt

    • This reply was modified 2 years, 11 months ago by Matt.
  • Participant
    Level: Initiated
    Posts: 6
    Matt on January 18, 2022 at 12:50 am #42655

    1) yes it is – exactly the same as my working site
    2) from the front end
    3) The broken site is actually using the same theme as my working site.

  • Participant
    Level: Initiated
    Posts: 6
    Matt on January 18, 2022 at 12:43 am #42653

    Which by the way, I do see the subsite-specific tables for my groups.

  • Participant
    Level: Initiated
    Posts: 6
    Matt on January 18, 2022 at 12:41 am #42652

    Thanks Brajesh, you’re right. Checking against another site I’d used this on, the described behavior was not observed.

    Is it possible I need to delete old tables in my DB Manager for the site in question? It was not configured immediately with the Multi Network plugin, but since its addition I have

    1) deactivated BuddyPress on each subsite
    2) added bp-custom with enable_multi
    3) network activated Buddy Multi Network
    4) single site activated BuddyPress on each subsite
    5) gone to settings>BuddyPress and clicked “save” on each subsite

    multiple times, in various sequences, however, I cannot get the groups to behave correctly. They do not all appear across subsites (so there is some “independence”), but they are being overwritten and the ID’s coming into conflict across subsites.